Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Reentrant flex & bison cherico@bonbon.net (2004-03-15) |
| Re: Reentrant flex & bison clint@0lsen.net (Clint Olsen) (2004-03-19) |
| Re: Reentrant flex & bison bonzini@gnu.org (2004-03-19) |
| Re: Reentrant flex & bison cherico@bonbon.net (2004-03-26) |
| Re: Reentrant flex & bison haberg@matematik.su.se (2004-04-03) |
| Re: Reentrant flex & bison eggert@twinsun.com (Paul Eggert) (2004-04-03) |
| Re: Reentrant flex & bison bonzini@gnu.org (2004-04-03) |
| [1 later articles] |
| From: | cherico@bonbon.net (cherico) |
| Newsgroups: | comp.compilers |
| Date: | 15 Mar 2004 09:39:37 -0500 |
| Organization: | http://groups.google.com |
| Keywords: | yacc, lex, question, comment |
| Posted-Date: | 15 Mar 2004 09:39:37 EST |
I am trying to write a reentrant scanner and parser using
flex and bison.
I discovered that the reentrance of flex is accomplished
by generating a c++ scanner class, while reentrant bison
remains the old c-style function call to yylex().
Anybody knows what the way to "glue" them (scanner & parser)
together is. flex and bison doesn't seem to co-work well
in this way, right?!
[Right. The C++ reentrant lex scanner doesn't talk to the
reentrant C bison parser. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.