From: skaller <skaller@users.sourceforge.net>
To: Keith Wansbrough <Keith.Wansbrough@cl.cam.ac.uk>
Cc: Jon Harrop <jdh30@cam.ac.uk>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocamlyacc reentrancy
Date: 06 May 2004 00:00:18 +1000 [thread overview]
Message-ID: <1083765617.20722.1099.camel@pelican.wigram> (raw)
In-Reply-To: <E1BLKwY-0003zP-00@mta1.cl.cam.ac.uk>
On Wed, 2004-05-05 at 21:52, Keith Wansbrough wrote:
> > On Sat, 2004-05-01 at 14:47, Jon Harrop wrote:
> >
> > Thanks for that link. Xavier says:
> >
> > "The module Parsing is supposed to be reentrant. Yes, there's some
> > global state inside, but we're careful to save and restore it across
> > entries. If you have a program demonstrating non-reentrance, please
> > send it to me privately and I'll try to fix that."
>
> What about multithreaded code?
The practical problem I have is that parsing C does
require *client* state to be passed around.
So the internal reentrancy of ocamlyacc parsers isn't
enough. The client has to wrap all the parses with
copyup/copy down code too... and they didn't.
If there been a state variable the authors might
have taken the trouble to use it.
Ocamllex lexers are now very easy to make reentrant!
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-05-05 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 3:08 skaller
2004-05-01 4:47 ` Jon Harrop
2004-05-01 5:36 ` skaller
2004-05-02 20:38 ` Eckart Goehler
2004-05-05 11:52 ` Keith Wansbrough
2004-05-05 14:00 ` skaller [this message]
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=1083765617.20722.1099.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=Keith.Wansbrough@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=jdh30@cam.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).