You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug#29348962: WARNING: POSIX YACC DOES NOT SUPPORT %YACC [-WYACC]
The modern Bison parser generator has started to output warnings
on the usage of some Bison extensions while the %yacc directive
(or the --yacc command line option) is enabled.
The current patch has neutralized that issue by disabling the
warning with --warnings=no-yacc.
Note: --yacc is still enabled, since this is necessary for the
generation of non-conflicting header files. With --yacc,
generated header files contain `#define` directives for each token,
while without --yacc there is the `enum yytokentype` declaration,
and two generated header files can conflict, since both contain
yytokentype.
In modern Bison releases, the name of yytokentype can be altered
with the `%define api.prefix {...}` directive, however releases
prior to 2.6 don't support that feature.
Other changes:
* %yacc directives have beed removed from *.yy files to not
duplicate the command line option --yacc (there was a Bison
warning).
* All warnings have been enabled with --warning=all where
applicable.
Change-Id: Ibee86ae996906dce25f30c755c5f9dfe3ea5bf00
0 commit comments