X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/f3bc338643cf15f345fa3a63811bd92869a42b89..0fe9720964da510a2b359af390a3053aace65f9f:/NEWS diff --git a/NEWS b/NEWS index 8cc36024..39c812e0 100644 --- a/NEWS +++ b/NEWS @@ -16,11 +16,11 @@ GNU Bison NEWS *** Enhancements of the -Werror option The -Werror=CATEGORY option is now recognized, and will treat specified - warnings as errors. The warnings need not have been explictly activated - using the -W option, this is similar to what gcc 4.7 does. + warnings as errors. The warnings need not have been explicitly activated + using the -W option, this is similar to what GCC 4.7 does. For example, given the following command line, Bison will treat both - warnings related to POSIX Yacc incompatiblities and S/R conflicts as + warnings related to POSIX Yacc incompatibilities and S/R conflicts as errors (and only those): $ bison -Werror=yacc,error=conflicts-sr input.y @@ -47,7 +47,7 @@ GNU Bison NEWS In the case of warnings treated as errors, the prefix is changed from "warning: " to "error: ", and the suffix is displayed, in a manner similar - to gcc, as [-Werror=CATEGORY]. + to GCC, as [-Werror=CATEGORY]. For instance, where the previous version of Bison would report (and exit with failure): @@ -240,7 +240,150 @@ 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 + + Warnings about uninitialized yylloc in yyparse have been fixed. + + Restored C90 compliance (yet no report was ever made). + +** Diagnostics are improved + +*** Changes in the format of error messages + + This used to be the format of many error reports: + + input.y:2.7-12: %type redeclaration for exp + input.y:1.7-12: previous declaration + + It is now: + + input.y:2.7-12: error: %type redeclaration for exp + input.y:1.7-12: previous declaration + +*** New format for error reports: carets + + Caret errors have been added to Bison: + + input.y:2.7-12: error: %type redeclaration for exp + %type exp + ^^^^^^ + input.y:1.7-12: previous declaration + %type exp + ^^^^^^ + + 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) + + The parse function now catches exceptions, uses the %destructors to + release memory (the lookahead symbol and the symbols pushed on the stack) + before re-throwing the exception. + + 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 @@ -256,18 +399,6 @@ GNU Bison NEWS All the generated headers are self-contained. -** 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 - - It is now: - - foo.y:5.10-25: result type clash on merge function 'merge': != - foo.y:4.13-27: previous declaration - ** Header guards (yacc.c, glr.c, glr.cc) In order to avoid collisions, the header guards are now @@ -279,15 +410,6 @@ GNU Bison NEWS will use YY_CALC_LIB_PARSE_H_INCLUDED as guard. -** Exception safety (lalr1.cc) - - The parse function now catches exceptions, uses the %destructors to - release memory (the lookahead symbol and the symbols pushed on the stack) - before rethrowing the exception. - - This feature is somewhat experimental. User feedback would be - appreciated. - ** Fix compiler warnings in the generated parser (yacc.c, glr.c) The compilation of pure parsers (%define api.pure) can trigger GCC @@ -305,21 +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) - - 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). - * Noteworthy changes in release 2.6.2 (2012-08-03) [stable] ** Bug fixes @@ -376,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. @@ -638,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): @@ -1154,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 @@ -1167,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: @@ -2178,7 +2288,7 @@ along with this program. If not, see . LocalWords: Automake TMPDIR LESSEQ ylwrap endif yydebug YYTOKEN YYLSP ival hh LocalWords: extern YYTOKENTYPE TOKENTYPE yytokentype tokentype STYPE lval pdf LocalWords: lang yyoutput dvi html ps POSIX lvalp llocp Wother nterm arg init - LocalWords: TOK calc yyo fval + LocalWords: TOK calc yyo fval Wconflicts Local Variables: mode: outline