From: SP <sp@orbitalfox.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Exceptions and Gc.
Date: Sat, 25 Mar 2017 11:11:41 +0000 [thread overview]
Message-ID: <1d614712-d4c8-c4ae-d796-993b32902d5e@orbitalfox.com> (raw)
In-Reply-To: <CABWZ6OQhCj9eErD7Fhng=JQtsCo7xU04veanZEOsW6kxs30LyQ@mail.gmail.com>
On 21/03/2017 15:07, Romain Beauxis wrote:
> Being able to clean everything up when the program exits seems like a
> reasonable feature.
Maybe the "appropriate" way with the current API is to have bindings
that deallocate the resources from the external heap, and only leave the
OCaml allocations (hopefully just pointers) to be collected later.
That way you can do any critical external finalisations at the exact
point you wish.
Would that work?
--
SP
prev parent reply other threads:[~2017-03-25 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 19:22 Romain Beauxis
2017-03-21 11:17 ` Dmitry Bely
2017-03-21 11:58 ` Max Mouratov
2017-03-21 15:07 ` Romain Beauxis
2017-03-21 16:05 ` Gabriel Scherer
2017-03-25 11:11 ` SP [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d614712-d4c8-c4ae-d796-993b32902d5e@orbitalfox.com \
--to=sp@orbitalfox.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox