caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <Damien.Doligez@inria.fr>
To: Maas-Maarten Zeeman <maas@wanadoo.nl>
Cc: Chris Hecker <checker@d6.com>,
	"Mary F. Fernandez" <mff@research.att.com>,
	caml-list@inria.fr, Jerome Simeon <simeon@research.bell-labs.com>
Subject: Re: [Caml-list] Question about register_global_root
Date: Sun, 1 Jun 2003 21:53:27 +0200	[thread overview]
Message-ID: <B6537C9E-946A-11D7-9CD8-0003930FCE12@inria.fr> (raw)
In-Reply-To: <3ED9DA78.4040601@wanadoo.nl>

On Sunday, June 1, 2003, at 12:50 PM, Maas-Maarten Zeeman wrote:

>  Chris Hecker wrote:
>
>>
>>>  handlers = (value *) malloc(sizeof(value));
>>>  register_global_root(handlers);
>>
>>
>> Shouldn't you init *handlers to Val_unit before calling 
>> register_global_root() as well?
>
> The manual explicitly tells that register_global_root should be called 
> before any valid value is stored in it for the first time, like 
> Val_unit. See Rule 4 of Interfacing C with Objective Caml in the 
> manual.
>
> So I think it is ok the way it is implemented.

I'm afraid Chris is right and the manual is wrong.

You can store Val_unit before you call register_global_root, because
Val_unit is not a pointer into the Caml heap.
You must store a valid value before the first allocation that follows
register_global_root.
You can store an allocated value (a pointer into the Caml heap) before
or after calling register_global_root, but it must be after the last
allocation that precedes register_global_root, and before the first
allocation that succeeds it.

At any rate, storing Val_unit before you call register_global_root is
safe and does not cost much CPU time.

-- Damien

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2003-06-01 19:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 19:45 Mary F. Fernandez
2003-05-28 19:51 ` Alexander V. Voinov
2003-05-28 20:33 ` Maas-Maarten Zeeman
2003-05-29  1:31   ` Jerome Simeon
2003-06-01  7:24   ` Chris Hecker
2003-06-01 10:50     ` Maas-Maarten Zeeman
2003-06-01 11:10       ` Chris Hecker
2003-06-01 19:53       ` Damien Doligez [this message]
2003-06-02 11:37         ` Jerome Simeon
2003-06-02 12:11           ` Maas-Maarten Zeeman
2003-06-02 12:19             ` [Caml-list] Am I mad?: OCaml for scientific scripting Siegfried Gonzi
2003-06-02 12:21             ` Siegfried Gonzi
2003-06-02 16:21         ` [Caml-list] Question about register_global_root Harry Chomsky
2003-06-02 20:02           ` Maas-Maarten Zeeman
2003-06-03  0:05             ` Chris Hecker
2003-06-01 19:19 ` Florian Douetteau

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=B6537C9E-946A-11D7-9CD8-0003930FCE12@inria.fr \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=checker@d6.com \
    --cc=maas@wanadoo.nl \
    --cc=mff@research.att.com \
    --cc=simeon@research.bell-labs.com \
    /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).