From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=AWL,HTML_MESSAGE,SPF_SOFTFAIL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id E99D6BC0A for ; Thu, 21 Jun 2007 12:34:40 +0200 (CEST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l5LAYd0F019100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Jun 2007 12:34:40 +0200 Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 9C3CE2043D; Thu, 21 Jun 2007 12:34:39 +0200 (CEST) X-AuditID: c1b4fb3e-b0835bb0000007e1-72-467a543f9dec Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 7C79E20208; Thu, 21 Jun 2007 12:34:39 +0200 (CEST) Received: from esealmw115.eemea.ericsson.se ([153.88.200.6]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 12:34:39 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7B3EF.C4F1EF85" Subject: RE: [Caml-list] ocaml dll in an Erlang runtime Date: Thu, 21 Jun 2007 12:34:38 +0200 Message-ID: <6616D98C65DD514BA2E1DDC5F92231550228B7C6@esealmw115.eemea.ericsson.se> In-Reply-To: <9f09a07a0706210315j1fc1f675yfdadf812c995da7f@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Caml-list] ocaml dll in an Erlang runtime Thread-Index: Acez7ct3qpiwS/fHSxuFDp9CeRfKZwAAQT0Q References: <6616D98C65DD514BA2E1DDC5F92231550228B6EB@esealmw115.eemea.ericsson.se> <9f09a07a0706210315j1fc1f675yfdadf812c995da7f@mail.gmail.com> From: "Ulf Wiger (TN/EAB)" To: "Matthieu Dubuget" , "Joel Reymont" Cc: X-OriginalArrivalTime: 21 Jun 2007 10:34:39.0215 (UTC) FILETIME=[C54E57F0:01C7B3EF] X-Brightmail-Tracker: AAAAAA== X-Miltered: at concorde with ID 467A5440.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; ocaml:01 erlang:01 runtime:01 ocaml:01 dlls:01 erlang:01 descriptors:01 matthieu:01 dubuget:01 runtime:01 compilation:01 dlls:01 descriptors:01 matthieu:01 dubuget:01 This is a multi-part message in MIME format. ------_=_NextPart_001_01C7B3EF.C4F1EF85 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable If you can run multiple instances of ocaml dlls in the same memory space, this doesn't have to be such a big deal. =20 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. =20 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. =20 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 =09 =09 2007/6/21, Joel Reymont :=20 My biggest issue with OCaml is building shared libraries. =09 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. =09 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... =09 The only problem I faced is that I have to avoid Thread module.=20 =09 Salutations =09 =09 Matt =09 ------_=_NextPart_001_01C7B3EF.C4F1EF85 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
If you=20 can run multiple instances of ocaml dlls in the same memory space, this = doesn't=20 have to be such a big deal.
 
To=20 clarify, a "driver" in Erlang is instantiated using the open_port(Cmd) = function.=20 This initiates a driver context, and the number of available file = descriptors=20 limits how many instances you can open. It becomes problematic if the = code=20 is makes use of global variables.
 
But=20 even if one can only have one instance of an OCaml driver, this could be = useful.=20 You can open a named port, which can be accessed by any erlang=20 process.
 
BR,
Ulf=20 W

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



2007/6/21, Joel Reymont <joelr1@gmail.com>:
My=20 biggest issue with OCaml is building shared libraries.

I = tried to=20 build a shared library for use with Ruby once and=20 failed
miserably.

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

I ask this, because almost all my OCaml code is use as shared=20 libraries.
Most of the time, this is on Windows (but compilation is = a lot=20 simpler on unix).
They are called from LabVIEW, Java, = C...

The only=20 problem I faced is that I have to avoid Thread module.=20 =

Salutations


Matt
------_=_NextPart_001_01C7B3EF.C4F1EF85--