Is there a replacement for yychar

Hi, I have a problem compiling my parser generated by Bison 3.0.2. For error recovery I use the lookahead variable `yychar' like this: ... | error { if (yychar != '}' && yychar != ';') yyclearin; else yyerrok; } ; But in commit 39be90223b73a42d249f99cdf283c4ab46a10a21 this variable

Re: Is there a replacement for yychar

> On 11 Dec 2014, at 19:17, Matthias Simon wrote: > > Hi, > > I have a problem compiling my parser generated by Bison 3.0.2. For error > recovery I use the lookahead variable `yychar' like this: > > ... >| error { if (yychar != '}' && yychar != ';') yyclearin; else yyerrok; } >; > >

Re: Is there a replacement for yychar

It is probably best to stick to the newer version only, to avoid bugs. Sadly, that is not really an option for me (due to outdated targets, high variety of developer-machines, difficulties with non-standard installations,...). Hence, I probably will workaround in the build-system like: if [ $

Re: How to implement optional semicolon rules

Hi again, I want to share my solution with you and the future generations stumbling across similar problems ;) I decided implementing the exact semicolon rules was not worth the trouble: - The grammar is already quite complex and difficult to understand, changing these to respect semicolon r