From: "Francois Rouaix" <francois.rouaix@gmail.com>
To: caml-list@inria.fr
Subject: Running OCaml code on (native) non-OCaml threads
Date: Fri, 14 Mar 2008 22:19:52 -0700 [thread overview]
Message-ID: <f2d6cc680803142219v155db88dwc0c6abe368f187c4@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Folks,Two years back, I asked about a situation where I wanted to run OCaml
code on threads created by a non-OCaml library, and the answer was that it
wasn't possible. Again today I'm facing the same situation, but this time I
believe there might be a way around it.
In theory, wouldn't it be possible to "attach" any posix thread to the OCaml
runtime, after the thread creation? The existing code isn't structured that
way (caml_thread_new, caml_thread_start), but superficially it looks like
one could set up the caml_thread_struct, if there isn't one for that thread
already. Am I missing something critical?
Thanks,
--f
[-- Attachment #2: Type: text/html, Size: 745 bytes --]
reply other threads:[~2008-03-15 5:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f2d6cc680803142219v155db88dwc0c6abe368f187c4@mail.gmail.com \
--to=francois.rouaix@gmail.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).