RE: [Caml-list] ocaml dll in an Erlang runtime

["Ulf Wiger (TN/EAB)" <ulf.wiger@ericsson.com>]

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

If you can run multiple instances of ocaml dlls in the same memory
space, this doesn't have to be such a big deal.
 
To clarify, a "driver" in Erlang is instantiated using the
open_port(Cmd) function. This initiates a driver context, and the number
of available file descriptors limits how many instances you can open. It
becomes problematic if the code is makes use of global variables.
 
But even if one can only have one instance of an OCaml driver, this
could be useful. You can open a named port, which can be accessed by any
erlang process.
 
BR,
Ulf W


________________________________

	From: caml-list-bounces@yquem.inria.fr
[mailto:caml-list-bounces@yquem.inria.fr] On Behalf Of Matthieu Dubuget
	Sent: den 21 juni 2007 12:16
	To: Joel Reymont
	Cc: caml-list@yquem.inria.fr
	Subject: Re: [Caml-list] ocaml dll in an Erlang runtime
	
	


	2007/6/21, Joel Reymont <joelr1@gmail.com>: 

		My biggest issue with OCaml is building shared
libraries.
		
		I tried to build a shared library for use with Ruby once
and failed
		miserably.


	Could you please elaborate about this? Maybe not on this thread.

	
	I ask this, because almost all my OCaml code is use as shared
libraries.
	Most of the time, this is on Windows (but compilation is a lot
simpler on unix).
	They are called from LabVIEW, Java, C...
	
	The only problem I faced is that I have to avoid Thread module. 
	
	Salutations
	
	
	Matt
	


[-- Attachment #2: Type: text/html, Size: 3077 bytes --]