From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
To: caml <caml-list@inria.fr>
Subject: [Caml-list] GC and interoperability with C
Date: Sun, 08 Jul 2001 21:59:44 -0700 [thread overview]
Message-ID: <3B493A40.1B2985FE@quasar.ipa.nw.ru> (raw)
Hi All,
>From what I see in the documentation, I see no way to 'lock' an OCaml
value on the heap so that it can be safely accessed from C code, and
then 'unlock' it, say, in the finalization function of some
Custom_block. In contrast to Python, e.g., where you just increment and
decrement the reference count.
Is this right?
If this is right, the interaction of OCaml to C becomes one-way, you
cannot safely access OCaml world from arbitrary C code.
Is this right?
Alexander
-------------------
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
next reply other threads:[~2001-07-09 5:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 4:59 Alexander V. Voinov [this message]
2001-07-09 6:59 ` Jacques Garrigue
[not found] ` <3B49C748.9CFB4E6@quasar.ipa.nw.ru>
[not found] ` <20010710094419W.garrigue@kurims.kyoto-u.ac.jp>
2001-07-10 0:46 ` Alexander V. Voinov
2001-07-12 5:47 ` Alexander V. Voinov
2001-07-12 7:34 ` Xavier Leroy
2001-07-12 15:42 ` Alexander V. Voinov
2001-07-09 22:08 Alexander V. Voinov
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=3B493A40.1B2985FE@quasar.ipa.nw.ru \
--to=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).