> Le 11 déc. 2014 à 19:17, Matthias Simon a écrit :
>
> 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; }
>;
>
> Le 8 nov. 2014 à 15:31, Evan Lavelle a écrit :
>
> Any idea how to fix this? I have a grammar which compiled without problems on
> bison 2.4.1/gcc 4.4.7 (RHEL 6.5), but which won't now compile on bison
> 3.0.2/gcc 4.8.2 (Ubuntu 14.04).
>
> The bison.tab.cc output from 2.4.1 included a defin
> Le 14 oct. 2014 à 18:21, Mike Aubury a écrit :
>
> Hi,
Hi Mike!
> I've just tried compiling our opensource software using bison 3.0.2 - and
> it seems %pure_parser isn't doing "what it used to do".
>
> I'm getting a "depreciated" message and told to change to "%pure-parser" -
> which i've d
> Le 29 sept. 2014 à 18:05, Kati Baker a écrit :
>
> All,
Hi Kati,
> Hello, I'm an undergrad CS student from West Virginia University, and I'm
> taking Compiler Construction this semester.
>
> In using Bison (I am using 3.0.2), I tried to run and compile an example my
> professor created in c