X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/342b8b6e2156e923797745af2da2596e3086ccd5..6cbfbcc58c425fef062c4d759e5d43c56a9a194e:/NEWS diff --git a/NEWS b/NEWS index af7d37d4..716f4090 100644 --- a/NEWS +++ b/NEWS @@ -1,7 +1,200 @@ Bison News ---------- -Changes in version 1.29d: +Changes in version 1.49b: + +* Undefined token + The undefined token was systematically mapped to 2 which prevented + the use of 2 from the user. This is no longer the case. + +* Undefined token + If yylex returned a code out of range, yyparse could die. This is + no longer the case. + +* Error token + According to POSIX, the error token should be numbered as 256. + Bison extends this requirement by making it a preference: *if* the + user specified that one of her tokens is numbered 256, then error + will be mapped onto another number. + +* Large grammars + Are now supported (large token numbers, large grammar size (= sum of + the LHS and RHS lengths), large LALR tables). + +* The initial rule is explicit. + Bison used to play hacks with the initial rule, which the user does + not write. It is now explicit, and visible in the reports and + graphs as rule 0. + +* Useless rules are actually removed. + Before, Bison reported the useless rules, but, although not used, + included them in the parsers. + +* False `Token not used' report fixed. + On a grammar such as + + %token useless useful + %% + exp: '0' %prec useful; + + where a token was used to set the precedence of the last rule, + bison reported both `useful' and `useless' as useless tokens. + +* Revert the C++ namespace changes introduced in 1.31, as they caused too + many portability hassles. + +* Items overflow + Bison no longer dumps core when there are too many items, it just + dies. + +* Token end-of-file + The token end of file may be specified by the user, in which case, + the user symbol is used in the reports, the graphs, and the verbose + error messages instead of `$', which remains being the defaults. + For instance + %token YYEOF 0 + or + %token YYEOF 0 "end of file" + +Changes in version 1.35, 2002-03-25: + +* C Skeleton + Some projects use Bison's C parser with C++ compilers, and define + YYSTYPE as a class. The recent adjustment of C parsers for data + alignment and 64 bit architectures made this impossible. + + Because for the time being no real solution for C++ parser + generation exists, kludges were implemented in the parser to + maintain this use. In the future, when Bison has C++ parsers, this + kludge will be disabled. + + This kludge also addresses some C++ problems when the stack was + extended. + + +Changes in version 1.34, 2002-03-12: + +* File name clashes are detected + $ bison foo.y -d -o foo.x + fatal error: header and parser would both be named `foo.x' + +* A missing `;' at the end of a rule triggers a warning + In accordance with POSIX, and in agreement with other + Yacc implementations, Bison will mandate this semicolon in the near + future. This eases the implementation of a Bison parser of Bison + grammars by making this grammar LALR(1) instead of LR(2). To + facilitate the transition, this release introduces a warning. + +* Revert the C++ namespace changes introduced in 1.31, as they caused too + many portability hassles. + +* DJGPP support added. + +* Fix test suite portability problems. + +Changes in version 1.33, 2002-02-07: + +* Fix C++ issues + Groff could not be compiled for the definition of size_t was lacking + under some conditions. + +* Catch invalid @n + As is done with $n. + +Changes in version 1.32, 2002-01-23: + +* Fix Yacc output file names + +* Portability fixes + +* Italian, Dutch translations + +Changes in version 1.31, 2002-01-14: + +* Many Bug Fixes + +* GNU Gettext and %expect + GNU Gettext asserts 10 s/r conflicts, but there are 7. Now that + Bison dies on incorrect %expectations, we fear there will be + too many bug reports for Gettext, so _for the time being_, %expect + does not trigger an error when the input file is named `plural.y'. + +* Use of alloca in parsers + If YYSTACK_USE_ALLOCA is defined to 0, then the parsers will use + malloc exclusively. Since 1.29, but was not NEWS'ed. + + alloca is used only when compiled with GCC, to avoid portability + problems as on AIX. + +* When the generated parser lacks debugging code, YYDEBUG is now 0 + (as POSIX requires) instead of being undefined. + +* User Actions + Bison has always permitted actions such as { $$ = $1 }: it adds the + ending semicolon. Now if in Yacc compatibility mode, the semicolon + is no longer output: one has to write { $$ = $1; }. + +* Better C++ compliance + The output parsers try to respect C++ namespaces. + [This turned out to be a failed experiment, and it was reverted later.] + +* Reduced Grammars + Fixed bugs when reporting useless nonterminals. + +* 64 bit hosts + The parsers work properly on 64 bit hosts. + +* Error messages + Some calls to strerror resulted in scrambled or missing error messages. + +* %expect + When the number of shift/reduce conflicts is correct, don't issue + any warning. + +* The verbose report includes the rule line numbers. + +* Rule line numbers are fixed in traces. + +* Swedish translation + +* Parse errors + Verbose parse error messages from the parsers are better looking. + Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'('' + Now: parse error: unexpected '/', expecting "number" or '-' or '(' + +* Fixed parser memory leaks. + When the generated parser was using malloc to extend its stacks, the + previous allocations were not freed. + +* Fixed verbose output file. + Some newlines were missing. + Some conflicts in state descriptions were missing. + +* Fixed conflict report. + Option -v was needed to get the result. + +* %expect + Was not used. + Mismatches are errors, not warnings. + +* Fixed incorrect processing of some invalid input. + +* Fixed CPP guards: 9foo.h uses BISON_9FOO_H instead of 9FOO_H. + +* Fixed some typos in the documentation. + +* %token MY_EOF 0 is supported. + Before, MY_EOF was silently renumbered as 257. + +* doc/refcard.tex is updated. + +* %output, %file-prefix, %name-prefix. + New. + +* --output + New, aliasing `--output-file'. + +Changes in version 1.30, 2001-10-26: * `--defines' and `--graph' have now an optionnal argument which is the output file name. `-d' and `-g' do not change, they do not take any @@ -10,11 +203,9 @@ Changes in version 1.29d: * `%source_extension' and `%header_extension' are removed, failed experiment. -* The test suite is more portable. - -* Better portability. - -Changes in version 1.29: +* Portability fixes. + +Changes in version 1.29, 2001-09-07: * The output file does not define const, as this caused problems when used with common autoconfiguration schemes. If you still use ancient compilers @@ -45,8 +236,11 @@ Changes in version 1.29: * New directives. `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose', `%debug', `%source_extension' and `%header_extension'. + +* @$ + Automatic location tracking. -Changes in version 1.28: +Changes in version 1.28, 1999-07-06: * Should compile better now with K&R compilers. @@ -78,7 +272,7 @@ Changes in version 1.26: * Generated parsers should now work even on operating systems which do not provide alloca(). -Changes in version 1.25: +Changes in version 1.25, 1995-10-16: * Errors in the input grammar are not fatal; Bison keeps reading the grammar file, and reports all the errors found in it. @@ -119,3 +313,28 @@ Changes in version 1.22: Changes in version 1.20: Output file does not redefine const for C++. + +Local Variables: +mode: outline +End: + +----- + +Copyright (C) 2001, 2002 Free Software Foundation, Inc. + +This file is part of GNU Autoconf. + +GNU Autoconf is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2, or (at your option) +any later version. + +GNU Autoconf is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with autoconf; see the file COPYING. If not, write to +the Free Software Foundation, Inc., 59 Temple Place - Suite 330, +Boston, MA 02111-1307, USA.