From: "EL CHAAR Rabih" <RABIH.ELCHAAR@sgam.com>
To: "Laurent Burgy" <burgy@enseirb.fr>, <caml-list@inria.fr>
Subject: RE: [Caml-list] ojacare known problem
Date: Fri, 27 May 2005 12:03:10 +0200 [thread overview]
Message-ID: <CE318D44F789304FBCC47CECBC4CD2841A0387@frdef-exmb01.europe.am.socgen> (raw)
Hello Laurent,
caml doesn't support multi-threaded calls since GC is not multithreaded (native threads).
Therefore, you should ensure that all the calls from java to caml are executed via a unique thread.
In the ojacare case, that would be the main thread.
Do you want multi-threaded java apps call caml ?
If you are interested by the subject, you can take a look at caml-list post where this question is raised.
[Caml-list] Using camljava library in a multithreaded context posted 23/02/2005
Hope this helps.
Rabih Chaar
-----Message d'origine-----
De : caml-list-admin@yquem.inria.fr
[mailto:caml-list-admin@yquem.inria.fr]De la part de Laurent Burgy
Envoyé : vendredi 27 mai 2005 11:25
À : caml-list@inria.fr
Objet : [Caml-list] ojacare known problem
Hi,
i am just wandering what kind of errors i would have if, sadly, i didn't
restraint communications between the Ocaml and Java to the main thread...
Does the "main" refer to the ocaml or the java one ?
thx
--
------------------------------------------------------------------------
Laurent BURGY Doctorant INRIA / LaBRI
Projet PHOENIX
------------------------------------------------------------------------
URL: http://phoenix.labri.fr/people/burgy
------------------------------------------------------------------------
_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
*************************************************************************
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
SG Asset Management et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie.
Decouvrez l'offre et les services de SG Asset Management sur le site
www.sgam.fr
********
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither SG Asset Management nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
*************************************************************************
reply other threads:[~2005-05-27 10:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CE318D44F789304FBCC47CECBC4CD2841A0387@frdef-exmb01.europe.am.socgen \
--to=rabih.elchaar@sgam.com \
--cc=burgy@enseirb.fr \
--cc=caml-list@inria.fr \
/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