> 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