* NEWS: Name some more contributors.
Restructure slightly.
* Noteworthy changes in release ?.? (????-??-??) [?]
* Noteworthy changes in release ?.? (????-??-??) [?]
+** 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 }
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.
for its own code, especially the definition of variables after statements.
The generated C parsers still aim at C90.
+** Backward incompatible changes
** Diagnostics are improved
** 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:
*** Changes in the format of error messages
This used to be the format of many error reports:
** Graph improvements in DOT and XSLT
** 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.
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.
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
Canonical LR, IELR, and LALR can suffer from a couple of problems
upon encountering a syntax error. First, the parser might perform
Tommy Nordgren tommy.nordgren@chello.se
Troy A. Johnson troyj@ecn.purdue.edu
Tys Lefering gccbison@gmail.com
Tommy Nordgren tommy.nordgren@chello.se
Troy A. Johnson troyj@ecn.purdue.edu
Tys Lefering gccbison@gmail.com
+Valentin Tolmer nitnelave1@gmail.com
Vin Shelton acs@alumni.princeton.edu
W.C.A. Wijngaards wouter@NLnetLabs.nl
Wayne Green wayne@infosavvy.com
Vin Shelton acs@alumni.princeton.edu
W.C.A. Wijngaards wouter@NLnetLabs.nl
Wayne Green wayne@infosavvy.com