From: Chris Hecker <checker@d6.com>
To: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>,
Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] register_global_root, malloc, etc.
Date: Wed, 15 Aug 2001 17:59:31 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20010815175549.02c293d0@shell16.ba.best.com> (raw)
In-Reply-To: <3B79DDC7.36D40AC3@quasar.ipa.nw.ru>
>I can't understand who will delete `foo *', allocated via `foo *p = new
>foo'?
free_foo unregisters the roots pointing inside foo, and then deletes foo. The GC will deallocate the abstract object itself.
> As I understood from the manual, Custom_tag is the only way to
>assign free_foo with the resulting Caml object.
Custom means the object gets a finalization call from the gc. Abstract means there's no finalization. I should be using Custom so my foo doesn't leak.
Chris
-------------------
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
prev parent reply other threads:[~2001-08-16 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 8:48 Chris Hecker
2001-08-14 8:25 ` Xavier Leroy
2001-08-15 2:26 ` Alexander V. Voinov
2001-08-16 0:59 ` Chris Hecker [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=4.3.2.7.2.20010815175549.02c293d0@shell16.ba.best.com \
--to=checker@d6.com \
--cc=Xavier.Leroy@inria.fr \
--cc=avv@quasar.ipa.nw.ru \
--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;
as well as URLs for NNTP newsgroup(s).