Thread View: gnu.utils.bug
1 messages
1 total messages
Started by cal
Sat, 10 Oct 1992 01:35
question about multiple uses of a bison parser
Author: cal
Date: Sat, 10 Oct 1992 01:35
Date: Sat, 10 Oct 1992 01:35
38 lines
1543 bytes
1543 bytes
i have two questions and a bug notification for version 1.10 i am trying to use a flex and bison parser to read several files in succession, and finding a problem with the state in which the parser is left after the first file is read on the second file, i get a message unexpected token "" at line 1 (i initialize yylineno before each parse, and the input file is closed after each parse) so, my two questions are: is this the right forum for questions of this type? how can i get the parser to read a real token instead of remembering an old one (which is what i think is going on)? separately, there appears to be a bug in the implementation of the "-t" flag - the generated C file has a line #define YYDEBUG but all the tests of YYDEBUG are of the form #if YYDEBUG != 0 which gets a "parse error" from the GNU C compiler either the definition should say #define YYDEBUG 1 or the tests should read #ifdef YYDEBUG (the former is the better solution) when i explicitly compile the generated file with -DDYYDEBUG, it works as i expected it to thanx much for any help more later, cal
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads