Re: Threadsafe parser generators?

paulpaul@knoware.nl (Paul Evenblij)
15 Dec 1996 16:23:09 -0500

          From comp.compilers

Related articles
Threadsafe parser generators? c.coles@slh0633.wins.icl.co.uk (Wilf Coles) (1996-12-07)
Re: Threadsafe parser generators? jlilley@empathy.com (1996-12-09)
Re: Threadsafe parser generators? Martin.Jourdan@inria.fr (1996-12-10)
Re: Threadsafe parser generators? car@mothra.lbl.gov (Chuck Rendleman) (1996-12-14)
Re: Threadsafe parser generators? meissner@cygnus.com (Michael Meissner) (1996-12-15)
Re: Threadsafe parser generators? paulpaul@knoware.nl (1996-12-15)
Re: Threadsafe parser generators? c.coles@slh0633.wins.icl.co.uk (Wilf Coles) (1996-12-24)
| List of all articles for this month |
From: paulpaul@knoware.nl (Paul Evenblij)
Newsgroups: comp.compilers
Date: 15 Dec 1996 16:23:09 -0500
Organization: Knoware Internet
References: 96-12-059
Keywords: parse, parallel

<c.coles@slh0633.wins.icl.co.uk> wrote:


> Does anyone know of any threadsafe parser generators (for C),
> i.e. that will generate parsers to work in a multi threaded
> environment.


I don't know if this might help:


The Yeech! LALR(1) parser generator was designed to produce code
without globals; all non-constant data is kept in a "parser parameter
block", which contains references to the parsing tables as well, and
which is passed to the (safe) parser driver routine.


However, as I said, I don't know if this really helps you, since in
its present release Yeech! is a CodeWarrior plugin for Macintosh, and
no standalone is yet available, let alone versions for other
platforms. Furthermore, the generated code would still need a minor
tweak, in order to make the parser really threadsafe.


But thanks for bringing up the subject. I'll add this to my to-do list
for a future release of Yeech. (This is the C version. The C++ version
will be threadsafe by default.)


<http://www.knoware.nl/users/paulpaul/dm/yeech10b1.html>


Paul Evenblij
paulpaul@knoware.nl
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.