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

Joakim Tjernlund joakim.tjernlund at transmode.se
Sun May 2 23:56:05 CEST 2010


Ondrej Zajicek <santiago at crfreenet.org> wrote on 2010/05/02 23:30:24:
>
> On Sun, May 02, 2010 at 11:09:32PM +0200, Joakim Tjernlund wrote:
> > > > 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 :)
> > >
> > > This is ugly and unnecessary workaround, i would rather keep this warning.
> >
> > Well, it is a defect in flex, not likely to be fixed anytime soon, and the
> > only remaining warning in the build. Would it not be good to remove that one too,
> > even if it is somewhat ugly? Then one would start to pay attention to all
> > warnings as there is normally no warnings.
>
> I usually pay attention to new warnings even if there are some small number
> of old unimportant 'persistent' warnings like these from flex output.

Not all are as you, especially newcomers. If there are warnings to begin
with one might just ignore them altogether, not even noticing any new ones.

 Jocke




More information about the Bird-users mailing list