From: "David McClain" <dmcclain1@mindspring.com>
To: <caml-list@inria.fr>
Subject: [Caml-list] Threading and C code
Date: Thu, 14 Jun 2001 11:36:41 -0700 [thread overview]
Message-ID: <00b201c0f500$f59483d0$210148bf@dylan> (raw)
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
next reply other threads:[~2001-06-14 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 18:36 David McClain [this message]
2001-06-18 9:43 ` Xavier Leroy
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='00b201c0f500$f59483d0$210148bf@dylan' \
--to=dmcclain1@mindspring.com \
--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).