From: Gaspard Bucher <gaspard@teti.ch>
To: David MENTRE <dmentre@linux-france.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml for embedding
Date: Mon, 12 Jul 2010 15:19:34 +0200 [thread overview]
Message-ID: <AANLkTiltvIH58qPFuPZS3yRWwj5x2c3EJGTTVNjjPNQP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinKQFHMeI6vbe9E2Dm9PZxpgQbLUKQFTv1rZJ4X@mail.gmail.com>
Thanks for the insight David.
I also found this email from Xavier Leroy
(http://caml.inria.fr/pub/ml-archives/caml-list/2002/11/64c14acb90cb14bedb2cacb73338fb15.en.html).
I will start with a single context (eventually built from several
scripts). If someone ever needs distributed computing, it's easy to
run several instances of Rubyk passing messages.
Just a final question on the topic: has JoCaml anything to do with
this concurrency (shared memory) question ?
Gaspard
On Mon, Jul 12, 2010 at 11:14 AM, David MENTRE <dmentre@linux-france.org> wrote:
> Hello,
>
> 2010/7/9 Gaspard Bucher <gaspard@teti.ch>:
>> From my understanding of the use of
>> caml_startup (or caml_main), this means that the caml runtime is
>> global.
>
> Yes.
>
>> Is there a way to avoid:
>>
>> 1. global locking (or locking only during script recompilation)
>
> I don't think so.
>
>> 2. script level encapsulation
>
> I don't know.
>
>
> You might play with the C symbols and a bit a C pre-processing to
> generate several different OCaml runtimes that would be linked with
> you application. But, as far as I know, the OCaml runtime has not be
> designed to be included several times within the same application.
>
> Sincerely yours,
> david
>
next prev parent reply other threads:[~2010-07-12 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 21:02 Gaspard Bucher
2010-07-09 7:06 ` [Caml-list] " David MENTRE
2010-07-09 10:29 ` Gaspard Bucher
2010-07-12 9:14 ` David MENTRE
2010-07-12 13:19 ` Gaspard Bucher [this message]
2010-07-20 0:36 ` Eray Ozkural
2010-07-20 15:02 ` Eray Ozkural
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=AANLkTiltvIH58qPFuPZS3yRWwj5x2c3EJGTTVNjjPNQP@mail.gmail.com \
--to=gaspard@teti.ch \
--cc=caml-list@yquem.inria.fr \
--cc=dmentre@linux-france.org \
/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