|Thread-safety, lex and yacc. firstname.lastname@example.org (Nicholas Dronen) (2001-03-31)|
|Re: Thread-safety, lex and yacc. email@example.com (2001-04-04)|
|Re: Thread-safety, lex and yacc. firstname.lastname@example.org (Troy Cauble) (2001-04-10)|
|Re: Thread-safety, lex and yacc. email@example.com (Clark) (2001-04-12)|
|From:||firstname.lastname@example.org (Clint Olsen)|
|Date:||4 Apr 2001 00:15:25 -0400|
|Organization:||Intel Corporation, Hillsboro, OR|
|Keywords:||lex, yacc, parallel|
|Posted-Date:||04 Apr 2001 00:15:25 EDT|
You can use Lemon http://www.hwaci.com/sw/lemon for a reentrant LALR(1)
parser generator and re2c http://www.tildeslash.org/re2c/index.html for a
reentrant scanner. If you need more help with this, please feel free to
send me mail. I have these two working together in a parser tool.
I haven't been able to find a reentrant LL(1) parser generator, however.
Nicholas Dronen wrote:
>Does anyone have experience with making an apparantly non-thread-safe
>lex/yacc code base thread-safe? Suggestions and pointers welcome.
Return to the
Search the comp.compilers archives again.