Hi,

I just wrote an bunch of C primitives to attach to an OCamlopt project, and
some of these wait on internal semaphores, events, and mutexes. It appeared
to me that these shut down the OCaml native threading system on Windows
(98SE and NT/4.0).

After searching through the sources for the threads lib I find that two
entry points are used to negotiate this possibility --
enter_blocking_section() and leave_blocking_section().  These appear to be
needed around any code that could possibly block.

These aren't mentioned in any of the normal header files in /ocaml/lib/caml
but I think they ought to be. Is this protocol subject to change? or can it
be made a standard protocol for C external functions?

- DM

-------------------
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