*** Obsolete features
- Support for YYFAIL is removed, as announced since Bison 2.4.2.
+ Support for YYFAIL is removed (deprecated in Bison 2.4.2).
Support for yystype and yyltype (instead of YYSTYPE and YYLTYPE)
- is removed, as announced in Bison 1.875.
+ is removed (deprecated in Bison 1.875).
+ Support for YYPARSE_PARAM is removed (deprecated in Bison 1.875).
** Warnings
-*** Warning categories are now displayed in warnings
+*** Warning categories are now displayed
For instance:
Also, it is possible to add code to the parser's constructors using
"%code init" and "%define init_throws".
-** C++ skeleton improvements
+** C++ skeletons improvements
+
+*** parser header (%defines) is no longer mandatory (lalr1.cc)
+
+ In which case, if needed, the support classes are defined in the generated
+ parser, instead of additional files (location.hh, position.hh and
+ stack.hh).
+
+*** locations are no longer mandatory (lalr1.cc, glr.cc)
+
+ Both lalr1.cc and glr.cc no longer require %location.
+
+*** syntax_error exception (lalr1.cc)
The C++ parser features a syntax_error exception, which can be
thrown from the scanner or from user rules to raise syntax errors.
* Noteworthy changes in release ?.? (????-??-??) [?]
+
+* Noteworthy changes in release 2.6.2 (2012-08-03) [stable]
+
+** Bug fixes
+
+ Buffer overruns, complaints from Flex, and portability issues in the test
+ suite have been fixed.
+
+** Spaces in %lex- and %parse-param (lalr1.cc, glr.cc)
+
+ Trailing end-of-lines in %parse-param or %lex-param would result in
+ invalid C++. This is fixed.
+
+** Spurious spaces and end-of-lines
+
+ The generated files no longer end (nor start) with empty lines.
+
+* Noteworthy changes in release 2.6.1 (2012-07-30) [stable]
+
Bison no longer executes user-specified M4 code when processing a grammar.
** Future Changes