mirror of
https://git.savannah.gnu.org/git/bison.git
synced 2026-03-09 12:23:04 +00:00
* NEWS: Instead of %union, you can define and use your own union type
YYSTYPE if your grammar contains at least one <type> tag. Your YYSTYPE need not be a macro; it can be a typedef. * doc/bison.texinfo (Value Type, Multiple Types, Location Type): (Union Decl, Decl Summary): Document this. * data/glr.c (YYSTYPE): Implement this. * data/glr.cc (YYSTYPE): Likewise. * data/lalr1.cc (YYSTYPE): Likewise. * data/yacc.c (YYSTYPE): Likewise. * src/output.c (prepare): Output tag_seen_flag. * src/parse-gram.y (declaration, grammar_declaration): Use 'union_seen' rather than 'typed' to determine whether %union has been seen, since grammars can now be typed without %union. (symbol_declaration, type.opt, symbol_def): Keep track of whether a tag has been seen. * src/reader.c (union_seen, tag_seen): New vars. (typed): remove. * src/reader.h (union_seen, tag_seen, typed): Likewise. * src/scan-code.l (untyped_var_seen): New variable. (handle_action_dollar): Adjust to above changes. (handle_action_dollar, handle_action_at): Improve overflow checking for outlandish numbers. * tests/input.at (AT_CHECK_UNUSED_VALUES): Redo test to avoid new diagnostics generated by above changes. * tests/regression.at (YYSTYPE typedef): Add test to check for type tags without %union.
This commit is contained in:
8
NEWS
8
NEWS
@@ -3,6 +3,12 @@ Bison News
|
||||
|
||||
Changes in version 2.3+:
|
||||
|
||||
* Instead of %union, you can define and use your own union type
|
||||
YYSTYPE if your grammar contains at least one <type> tag.
|
||||
Your YYSTYPE need not be a macro; it can be a typedef.
|
||||
This change is for compatibility with other Yacc implementations,
|
||||
and is required by POSIX.
|
||||
|
||||
* Locations columns and lines start at 1.
|
||||
In accordance with the GNU Coding Standards and Emacs.
|
||||
|
||||
@@ -19,7 +25,7 @@ Changes in version 2.3+:
|
||||
`%{ ... %}' syntax. To generate the pre-prologue, Bison concatenates all
|
||||
prologue blocks that you've declared before the first %union. To generate
|
||||
the post-prologue, Bison concatenates all prologue blocks that you've
|
||||
declared after the first %union.
|
||||
declared after the first %union.
|
||||
|
||||
Previous releases of Bison inserted the pre-prologue into both the header
|
||||
file and the code file in all cases except for LALR(1) parsers in C. In the
|
||||
|
||||
Reference in New Issue
Block a user