* Noteworthy changes in release ?.? (????-??-??) [?]
-** Future changes
+** WARNING: Future backward-incompatibilities!
- Bison will stop adding a semicolon at the end of the actions:
+ Bison will stop adding a semicolon at the end of the actions (as announced
+ in the release 2.5):
foo.y:2.22: warning: a ';' might be needed at the end of action code
exp: "num" { $$ = $1 }
for its own code, especially the definition of variables after statements.
The generated C parsers still aim at C90.
-** Incompatible changes
+** Backward incompatible changes
*** Obsolete features
This is has been fixed: yylval, yynerrs, yychar, and yylloc are now valid
identifiers for user-provided variables.
+*** stdio.h is no longer needed when locations are enabled (yacc.c)
+
+ Changes in Bison 2.7 introduced a dependency on FILE and fprintf when
+ locations are enabled. This is fixed.
+
** Diagnostics reported by Bison
Most of these features were contributed by Théophile Ranquet and Victor
It used to be an error only if used in non GLR mode, _and_ if there are
reduce/reduce conflicts.
+** Token numbering has changed to preserve the user-defined order
+
+ When declaring %token A B, the numbering for A is inferior to B. Up to now,
+ when declaring associativity at the same time, with %left (or %right,
+ %precedence, %nonassoc), B was inferior to A.
+
* Noteworthy changes in release 2.7 (2012-12-12) [stable]
** Bug fixes
** Diagnostics are improved
+ Contributed by Théophile Ranquet.
+
*** Changes in the format of error messages
This used to be the format of many error reports:
** Graph improvements in DOT and XSLT
+ Contributed by Théophile Ranquet.
+
The graphical presentation of the states is more readable: their shape is
now rectangular, the state number is clearly displayed, and the items are
numbered and left-justified.
These features are experimental. More user feedback will help to
stabilize them.
-** LAC (Lookahead Correction) for syntax error handling:
+** LAC (Lookahead Correction) for syntax error handling
+
+ Contributed by Joel E. Denny.
Canonical LR, IELR, and LALR can suffer from a couple of problems
upon encountering a syntax error. First, the parser might perform