From: Xavier Leroy <xavier.leroy@inria.fr>
To: Jeff Henrikson <jehenrik@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: SysThreads and DLL's
Date: Sat, 8 Dec 2001 17:28:38 +0100 [thread overview]
Message-ID: <20011208172838.B5229@pauillac.inria.fr> (raw)
In-Reply-To: <003601c17c55$a0493060$0b01a8c0@mit.edu>; from jehenrik@yahoo.com on Mon, Dec 03, 2001 at 06:52:54PM -0500
> I also need to expose caml code in a DLL. Could you post your
> working thread code/event loop so that I can avoid hacking around?
> Do you have any idea what will happen with windows dynamic linking
> behavior if two such DLLs get loaded into the same process space?
> It'd be cool if they could share runtimes, but I doubt that would be
> an easy or free behavior. I'm not even sure you would get correct
> separation of two runtimes for free. I'd have to test the linker
> scoping behavior.
If David McClain encapsulated his Caml code in a Win32 DLL the way I
expect he did, each such DLL comes with its own copy of the Caml
runtime system, allocates its own Caml heap, and doesn't share
anything with any other Caml-encapsulated DLL. On the surface, this
might look a bit wasteful in resources, but it sure makes things
easier and more robust.
- Xavier Leroy
-------------------
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 prev parent reply other threads:[~2001-12-08 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 23:52 Jeff Henrikson
2001-12-08 16:28 ` Xavier Leroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 9:57 David McClain
2001-12-02 5:08 ` David McClain
2001-12-02 15:42 ` Julian Assange
2001-12-02 17:45 ` David McClain
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=20011208172838.B5229@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=jehenrik@yahoo.com \
/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).