On Tue, Nov 15, 2005 at 02:03:20AM +0000, xuzq wrote:
> Yes,it 's ok without threads and i see perl4caml may not be
> thread-safe.I 'm only curious about why only "eval" crashes and
> "call" looks fine.In my program another thread run the following
> code without any error.

I'm guessing that 'call' works by luck.

I had a quick scan of the code and I can't see anything obviously
unsafe.  Since I never release the OCaml lock in any of the C code,
surely the C calls are all serialised?  It might also be that
perl4caml_init is being called twice (from two threads) which would
probably cause bad things to happen.  A simple print statement should
diagnose whether this is the case.

To be honest, I'm not sure what the threading issues are when calling
external C libraries.  I rarely even use threading in OCaml, and as
you probably guessed, I've never used it at all from perl4caml.

> Thank you for your excellent perl4caml,Richard!Would it be possible for perl
> to callocaml code just like the Inline::OCaml thoughts in that post:
> http://caml.inria.fr/pub/ml-archives/caml-list/2002/02/e363d76f1e9b94779b1ffe7de3a7c011.en.html?

Inline::OCaml would certainly be nice to have, but I don't have the
time, or possibly even the skills, to write it.

Rich.

-- 
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com