From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: bouyssou@didac-mip.fr
Cc: caml-list@inria.fr
Subject: Re: camlex/camlyacc + threads problem
Date: Thu, 18 Sep 1997 16:18:26 +0200 (MET DST) [thread overview]
Message-ID: <199709181418.QAA21587@pauillac.inria.fr> (raw)
In-Reply-To: <199709100817.KAA05734@yeti.didac-mip.fr> from Olivier Bouyssou at "Sep 10, 97 10:17:24 am"
> I've a problem when I use a parser in multiple threads. If the calls to the
> parser are not enclosed by a mutex, there are parse errors. ( See example in
> french version )
Of course. Most of the O'Caml standard library is *not* thread-safe
yet. So far, everything in Pervasives is thread-safe, in particular
I/O, but other stateful libraries are not. This includes in
particular Hashtbl, Queue, and Lexing.
There are no easy ways to make a library thread-safe and still have it
working in the non-threaded case. So, I'm not promising these
problems will be fixed soon.
In the meantime, use mutexes liberally, or make sure that only one
thread is doing e.g. parsing.
- Xavier Leroy
next prev parent reply other threads:[~1997-09-22 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-10 8:17 Olivier Bouyssou
1997-09-18 14:18 ` Xavier Leroy [this message]
1997-09-16 14:25 Thierry Bravier
[not found] <199709231254.OAA20307@yeti2.didac-mip.fr>
1997-09-25 12:19 ` Xavier Leroy
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=199709181418.QAA21587@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=bouyssou@didac-mip.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