Browse thread
[Caml-list] GC and interoperability with C
- Alexander V. Voinov
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Alexander V. Voinov <avv@q...> |
| Subject: | [Caml-list] GC and interoperability with C |
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