X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/fc4fdd623e7613c002f7c7d6cb73b4ab4bb5b494..235892350f6547e5c6a350b85561eda14409a0b5:/NEWS diff --git a/NEWS b/NEWS index d1b66564..cecc6760 100644 --- a/NEWS +++ b/NEWS @@ -2,19 +2,50 @@ GNU Bison NEWS * Noteworthy changes in release ?.? (????-??-??) [?] + +* Noteworthy changes in release 2.6.90 (2012-12-07) [beta] + ** 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. +** %language is no longer an experimental feature. - Stray Info files shipped by accident are removed. + The introduction of this feature, in 2.4, was four years ago. The --language + option and the %language directive are no longer experimental. - Incorrect definitions of YY_, issued by yacc.c when no parser header is - generated, are removed. +** New format for error reports: carets - All the generated headers are self-contained. + Caret errors have been added to Bison, for example (taken from the + documentation): + + 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 -fall of -fcaret. 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". ** Changes in the format of error messages @@ -28,17 +59,6 @@ GNU Bison NEWS 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 - 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. - ** Exception safety (lalr1.cc) The parse function now catches exceptions, uses the %destructors to @@ -48,23 +68,6 @@ GNU Bison NEWS 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 - warnings such as: - - input.c: In function 'yyparse': - input.c:1503:12: warning: 'yylval' may be used uninitialized in this - function [-Wmaybe-uninitialized] - *++yyvsp = yylval; - ^ - - This is now fixed; pragmas to avoid these warnings are no longer needed. - - Warnings from clang ("equality comparison with extraneous parentheses" and - "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 @@ -84,7 +87,7 @@ GNU Bison NEWS position_type are deprecated in favor of api.location.type and api.position.type. -** Graphviz improvements +** 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 @@ -93,6 +96,83 @@ GNU Bison NEWS 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. + + Two nodes were added to the documentation: Xml and Graphviz. + +** Documentation + + The sections about shift/reduce and reduce/reduce conflicts resolution + have been fixed and extended. + +* 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 + warnings such as: + + input.c: In function 'yyparse': + input.c:1503:12: warning: 'yylval' may be used uninitialized in this + function [-Wmaybe-uninitialized] + *++yyvsp = yylval; + ^ + + This is now fixed; pragmas to avoid these warnings are no longer needed. + + Warnings from clang ("equality comparison with extraneous parentheses" and + "function declared 'noreturn' should not return") have also been + addressed. + * Noteworthy changes in release 2.6.2 (2012-08-03) [stable] ** Bug fixes