[PATCH 1/2] flex: Avoid REJECT name conflict.

Joakim Tjernlund joakim.tjernlund at transmode.se
Fri Apr 30 18:29:22 CEST 2010


Martin Mares <mj at ucw.cz> wrote on 2010/04/29 22:14:16:
>
> Hello!
>
> > `flex' scans your rule actions to determine whether you use the
> > `REJECT' or `yymore()' features.  The `REJECT' and `yymore' options are
> > available to override its decision as to whether you use the options,
> > either by setting them (e.g., `%option reject)' to indicate the feature
> > is indeed used, or unsetting them to indicate it actually is not used
> > (e.g., `%option noyymore)'.
>
> BTW, wouldn't a simple `%option noreject' suffice?

So what was the end conclusion on this, will you add
 %option noinput
 %option nounput
 %option noreject
?
Then the only warning left is the one fixed with
 #define YY_FATAL_ERROR(msg) do {cf_error(msg); if(0) yy_fatal_error(msg); } while(0)
Not ideal, but the try convincing flex of that :)




More information about the Bird-users mailing list