caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Quinn <cq@htec.demon.co.uk>
To: CAML LIST <caml-list@inria.fr>, caml@inria.fr
Subject: [Caml-list] fumbling with Gc.finalise
Date: Mon, 01 Oct 2001 22:12:41 +0100	[thread overview]
Message-ID: <3BB8DC49.F82FE7D8@htec.demon.co.uk> (raw)

Hi TeamCaml,

I've been using this function quite a bit now I've discovered it.
I thought I'd captured the dependencies between a bunch of related resource handles such as to guarantee orderly resource release. But I've just been bitten and realised that if a bunch of values are no longer reachable from the rest of the program, 
no account is taken of the pointer relationships existing between them. Thus there is no guaranteed running order of the finalisation functions.

Would it not be more reasonable to treat the argument and finalisation closure as roots until the latter has actually completed execution?

Thanks,
Chris Q.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


             reply	other threads:[~2001-10-01 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 21:12 Chris Quinn [this message]
2001-10-05 12:04 Damien Doligez

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=3BB8DC49.F82FE7D8@htec.demon.co.uk \
    --to=cq@htec.demon.co.uk \
    --cc=caml-list@inria.fr \
    --cc=caml@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;
as well as URLs for NNTP newsgroup(s).