Re: Bison 1.35 bug

[Akim Demaille]

>>>>> "Yiping" == Yiping Guan <address@hidden> writes:

Yiping> I have an application which uses bison 1.35 generated parser
Yiping> to read a input file.

Yiping> If the file has correct syntax, everything is fine.

Yiping> If a file has wrong content, error message "parse error" is
Yiping> displayed, which is expected. However, once we get an syntax
Yiping> error from one input file, we cannot open a following input
Yiping> file which has correct syntax. I have to re-start the
Yiping> application in order to open a correct input file.

Yiping> Could you please help me to debug the parser? Or tell me how
Yiping> to fix the problem.

Could you equip your parser with YYDEBUG and see what it displays?  I
wouldn't be surprised if the real problem was with the scanner, not
the parser.

As far as I can see, 1.35 does properly reset all its variables:

  YYDPRINTF ((stderr, "Starting parse\n"));

  yystate = 0;
  yyerrstatus = 0;
  yynerrs = 0;
  yychar = YYEMPTY;             /* Cause a token to be read.  */

so it is something else.

Are you sure your scanner is properly reset? Including possible start
conditions reset to INITIAL if you use Lex etc.