From: Christophe TROESTLER <Christophe.Troestler+ocaml@umh.ac.be>
To: goswin-v-b@web.de
Cc: edwintorok@gmail.com, caml-list@yquem.inria.fr, kecheng@cecs.pdx.edu
Subject: Re: [Caml-list] OCaml memory leak issue
Date: Thu, 25 Nov 2010 08:42:50 +0100 (CET) [thread overview]
Message-ID: <20101125.084250.936894655214001480.Christophe.Troestler+ocaml@umons.ac.be> (raw)
In-Reply-To: <87lj4ipcqk.fsf@frosties.localnet>
On Wed, 24 Nov 2010 23:40:03 +0100, Goswin von Brederlow wrote:
>
> In case of custom blocks and finalize function I believe this to be an
> error. Managing resources that the OS does not free (IPC tokens,
> tempfiles, ...) is made much harder due to this.
You also have "at_exit" and weak pointers which can help you to do that.
Best,
C.
prev parent reply other threads:[~2010-11-25 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 3:54 Kecheng
2010-11-24 4:06 ` [Caml-list] " Edgar Friendly
2010-11-24 7:30 ` Török Edwin
2010-11-24 22:40 ` Goswin von Brederlow
2010-11-24 23:41 ` DS
2010-11-25 13:27 ` Goswin von Brederlow
2010-11-25 7:42 ` Christophe TROESTLER [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=20101125.084250.936894655214001480.Christophe.Troestler+ocaml@umons.ac.be \
--to=christophe.troestler+ocaml@umh.ac.be \
--cc=caml-list@yquem.inria.fr \
--cc=edwintorok@gmail.com \
--cc=goswin-v-b@web.de \
--cc=kecheng@cecs.pdx.edu \
/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;
as well as URLs for NNTP newsgroup(s).