X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/d949eefdd3cfa8087e3c7541a357bfd40d9ddcd8..a89a5b1442d6e9fecb306725a2f5426d9f3fbf90:/NEWS diff --git a/NEWS b/NEWS index 346c4da4..39c812e0 100644 --- a/NEWS +++ b/NEWS @@ -240,44 +240,89 @@ GNU Bison NEWS It used to be an error only if used in non GLR mode, _and_ if there are reduce/reduce conflicts. -* Noteworthy changes in release ?.? (????-??-??) [?] +* Noteworthy changes in release 2.7 (2012-12-12) [stable] ** Bug fixes - Bugs and portability issues in the test suite have been fixed. + Warnings about uninitialized yylloc in yyparse have been fixed. - Some errors in translations have been addressed, and --help now directs - users to the appropriate place to report them. + Restored C90 compliance (yet no report was ever made). - Stray Info files shipped by accident are removed. +** Diagnostics are improved - Incorrect definitions of YY_, issued by yacc.c when no parser header is - generated, are removed. - - All the generated headers are self-contained. - -** Changes in the format of error messages +*** Changes in the format of error messages This used to be the format of many error reports: - foo.y:5.10-24: result type clash on merge function 'merge': != - foo.y:4.13-27: previous declaration + input.y:2.7-12: %type redeclaration for exp + input.y:1.7-12: previous declaration It is now: - foo.y:5.10-25: result type clash on merge function 'merge': != - foo.y:4.13-27: previous declaration + input.y:2.7-12: error: %type redeclaration for exp + input.y:1.7-12: previous declaration -** Header guards (yacc.c, glr.c, glr.cc) +*** New format for error reports: carets - In order to avoid collisions, the header guards are now - YY___INCLUDED, instead of merely _. - For instance the header generated from + Caret errors have been added to Bison: - %define api.prefix "calc" - %defines "lib/parse.h" + input.y:2.7-12: error: %type redeclaration for exp + %type exp + ^^^^^^ + input.y:1.7-12: previous declaration + %type exp + ^^^^^^ - will use YY_CALC_LIB_PARSE_H_INCLUDED as guard. + or + + input.y:3.20-23: error: ambiguous reference: '$exp' + exp: exp '+' exp { $exp = $1 + $3; }; + ^^^^ + input.y:3.1-3: refers to: $exp at $$ + exp: exp '+' exp { $exp = $1 + $3; }; + ^^^ + input.y:3.6-8: refers to: $exp at $1 + exp: exp '+' exp { $exp = $1 + $3; }; + ^^^ + input.y:3.14-16: refers to: $exp at $3 + exp: exp '+' exp { $exp = $1 + $3; }; + ^^^ + + The default behaviour for now is still not to display these unless + explictly asked with -fcaret (or -fall). However, in a later release, it + will be made the default behavior (but may still be deactivated with + -fno-caret). + +** New value for %define variable: api.pure full + + The %define variable api.pure requests a pure (reentrant) parser. However, + for historical reasons, using it in a location-tracking Yacc parser + resulted in a yyerror function that did not take a location as a + parameter. With this new value, the user may request a better pure parser, + where yyerror does take a location as a parameter (in location-tracking + parsers). + + The use of "%define api.pure true" is deprecated in favor of this new + "%define api.pure full". + +** New %define variable: api.location.type (glr.cc, lalr1.cc, lalr1.java) + + The %define variable api.location.type defines the name of the type to use + for locations. When defined, Bison no longer generates the position.hh + and location.hh files, nor does the parser will include them: the user is + then responsible to define her type. + + This can be used in programs with several parsers to factor their location + and position files: let one of them generate them, and the others just use + them. + + This feature was actually introduced, but not documented, in Bison 2.5, + under the name "location_type" (which is maintained for backward + compatibility). + + For consistency, lalr1.java's %define variables location_type and + position_type are deprecated in favor of api.location.type and + api.position.type. ** Exception safety (lalr1.cc) @@ -288,6 +333,83 @@ GNU Bison NEWS This feature is somewhat experimental. User feedback would be appreciated. +** Graph improvements in DOT and XSLT + + 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 reductions are now explicitly represented as transitions to other + diamond shaped nodes. + + These changes are present in both --graph output and xml2dot.xsl XSLT + processing, with minor (documented) differences. + +** %language is no longer an experimental feature. + + The introduction of this feature, in 2.4, was four years ago. The + --language option and the %language directive are no longer experimental. + +** Documentation + + The sections about shift/reduce and reduce/reduce conflicts resolution + have been fixed and extended. + + Although introduced more than four years ago, XML and Graphviz reports + were not properly documented. + + The translation of mid-rule actions is now described. + +* Noteworthy changes in release 2.6.5 (2012-11-07) [stable] + + We consider compiler warnings about Bison generated parsers to be bugs. + Rather than working around them in your own project, please consider + reporting them to us. + +** Bug fixes + + Warnings about uninitialized yylval and/or yylloc for push parsers with a + pure interface have been fixed for GCC 4.0 up to 4.8, and Clang 2.9 to + 3.2. + + Other issues in the test suite have been addressed. + + Nul characters are correctly displayed in error messages. + + When possible, yylloc is correctly initialized before calling yylex. It + is no longer necessary to initialize it in the %initial-action. + +* Noteworthy changes in release 2.6.4 (2012-10-23) [stable] + + Bison 2.6.3's --version was incorrect. This release fixes this issue. + +* Noteworthy changes in release 2.6.3 (2012-10-22) [stable] + +** Bug fixes + + Bugs and portability issues in the test suite have been fixed. + + Some errors in translations have been addressed, and --help now directs + users to the appropriate place to report them. + + Stray Info files shipped by accident are removed. + + Incorrect definitions of YY_, issued by yacc.c when no parser header is + generated, are removed. + + All the generated headers are self-contained. + +** Header guards (yacc.c, glr.c, glr.cc) + + In order to avoid collisions, the header guards are now + YY___INCLUDED, instead of merely _. + For instance the header generated from + + %define api.prefix "calc" + %defines "lib/parse.h" + + will use YY_CALC_LIB_PARSE_H_INCLUDED as guard. + ** Fix compiler warnings in the generated parser (yacc.c, glr.c) The compilation of pure parsers (%define api.pure) can trigger GCC @@ -305,25 +427,6 @@ GNU Bison NEWS "function declared 'noreturn' should not return") have also been addressed. -** New %define variable: api.location.type (glr.cc, lalr1.cc, lalr1.java) - - The %define variable api.location.type defines the name of the type to use - for locations. When defined, Bison no longer generates the position.hh - and location.hh files, nor does the parser will include them: the user is - then responsible to define her type. - - This can be used in programs with several parsers to factor their location - and position files: let one of them generate them, and the others just use - them. - - This feature was actually introduced, but not documented, in Bison 2.5, - under the name "location_type" (which is maintained for backward - compatibility). - - For consistency, lalr1.java's %define variables location_type and - position_type are deprecated in favor of api.location.type and - api.position.type. - * Noteworthy changes in release 2.6.2 (2012-08-03) [stable] ** Bug fixes @@ -380,7 +483,7 @@ GNU Bison NEWS * Noteworthy changes in release 2.6 (2012-07-19) [stable] -** Future changes: +** Future changes The next major release of Bison will drop support for the following deprecated features. Please report disagreements to bug-bison@gnu.org. @@ -642,6 +745,7 @@ GNU Bison NEWS These features are experimental in this version. More user feedback will help to stabilize them. + Contributed by Alex Rozenman. ** IELR(1) and canonical LR(1): @@ -1158,6 +1262,7 @@ GNU Bison NEWS The current Java interface is experimental and may evolve. More user feedback will help to stabilize it. + Contributed by Paolo Bonzini. ** %language @@ -1171,6 +1276,7 @@ GNU Bison NEWS Bison can now generate an XML report of the LALR(1) automaton using the new "--xml" option. The current XML schema is experimental and may evolve. More user feedback will help to stabilize it. + Contributed by Wojciech Polak. ** The grammar file may now specify the name of the parser header file using %defines. For example: