Bison News
----------
-Changes in version 1.875e:
+Changes in version 2.0a, 2005-05-22:
-* New directive: %initial-action.
- This directive allows the user to run arbitrary code (including
- initializing @$) from yyparse before parsing starts.
+* Bison-generated C parsers use the _ macro to translate strings from
+ English to the user's language, e.g., _("syntax error"). By default,
+ _ is defined to be a no-op macro so the strings are not translated.
-* The option `--report=lookahead' was changed to `--report=look-ahead'.
- The old spelling still works, but is not documented and will be
- removed.
+* When generating verbose diagnostics, Bison-generated C parsers no longer
+ quote the literal strings associated with tokens. For example, for
+ a syntax error associated with '%token NUM "number"' they might
+ print 'syntax error, unexpected number' instead of 'syntax error,
+ unexpected "number"'.
-* Error token location.
- During error recovery, the location of the syntax error is updated
- to cover the whole sequence covered by the error token: it includes
- the shifted symbols thrown away during the first part of the error
- recovery, and the lookahead rejected during the second part.
+Changes in version 2.0, 2004-12-25:
-* Goto numbers are no longer arbitrarily limited to 16-bit counts.
+* Possibly-incompatible changes
-Changes in version 1.875d, 2004-05-21:
+ - Bison-generated parsers no longer default to using the alloca function
+ (when available) to extend the parser stack, due to widespread
+ problems in unchecked stack-overflow detection. You can "#define
+ YYSTACK_USE_ALLOCA 1" to require the use of alloca, but please read
+ the manual to determine safe values for YYMAXDEPTH in that case.
-* Unescaped newlines are no longer allowed in character constants or
- string literals. They were never portable, and GCC 3.4.0 has
- dropped support for them. Better diagnostics are now generated if
- forget a closing quote.
+ - Error token location.
+ During error recovery, the location of the syntax error is updated
+ to cover the whole sequence covered by the error token: it includes
+ the shifted symbols thrown away during the first part of the error
+ recovery, and the lookahead rejected during the second part.
-* NUL bytes are no longer allowed in Bison string literals, unfortunately.
+ - Semicolon changes:
+ . Stray semicolons are no longer allowed at the start of a grammar.
+ . Semicolons are now required after in-grammar declarations.
-* %token numbers can now be hexadecimal integers, e.g., `%token FOO 0x12d'.
- This is a GNU extension.
+ - Unescaped newlines are no longer allowed in character constants or
+ string literals. They were never portable, and GCC 3.4.0 has
+ dropped support for them. Better diagnostics are now generated if
+ forget a closing quote.
-* A new directive "%expect-rr N" specifies the expected number of
- reduce/reduce conflicts in GLR parsers.
+ - NUL bytes are no longer allowed in Bison string literals, unfortunately.
-* Experimental %destructor support has been added to lalr1.cc.
+* New features
-Changes in version 1.875c, 2003-08-25:
+ - GLR grammars now support locations.
- (Just bug fixes.)
+ - New directive: %initial-action.
+ This directive allows the user to run arbitrary code (including
+ initializing @$) from yyparse before parsing starts.
-Changes in version 1.875b, 2003-06-17:
+ - A new directive "%expect-rr N" specifies the expected number of
+ reduce/reduce conflicts in GLR parsers.
-* GLR grammars now support locations.
+ - %token numbers can now be hexadecimal integers, e.g., `%token FOO 0x12d'.
+ This is a GNU extension.
-* Semicolon changes:
- - Semicolons are now allowed before "|" in grammar rules, as POSIX requires.
- - Stray semicolons are no longer allowed at the start of a grammar.
- - Semicolons are now required after in-grammar declarations.
+ - The option `--report=lookahead' was changed to `--report=look-ahead'.
+ The old spelling still works, but is not documented and will be
+ removed.
+
+ - Experimental %destructor support has been added to lalr1.cc.
+
+ - New configure option --disable-yacc, to disable installation of the
+ yacc command and -ly library introduced in 1.875 for POSIX conformance.
-Changes in version 1.875a, 2003-02-01:
+* Bug fixes
-* For now, %expect-count violations are now just warnings, not errors.
- This is for compatibility with Bison 1.75 and earlier (when there are
- reduce/reduce conflicts) and with Bison 1.30 and earlier (when there
- are too many or too few shift/reduce conflicts). However, in future
- versions of Bison we plan to improve the %expect machinery so that
- these violations will become errors again.
+ - For now, %expect-count violations are now just warnings, not errors.
+ This is for compatibility with Bison 1.75 and earlier (when there are
+ reduce/reduce conflicts) and with Bison 1.30 and earlier (when there
+ are too many or too few shift/reduce conflicts). However, in future
+ versions of Bison we plan to improve the %expect machinery so that
+ these violations will become errors again.
-* New configure option --disable-yacc, to disable installation of the
- yacc command and -ly library introduced in 1.875 for POSIX conformance.
+ - Within Bison itself, numbers (e.g., goto numbers) are no longer
+ arbitrarily limited to 16-bit counts.
+
+ - Semicolons are now allowed before "|" in grammar rules, as POSIX requires.
\f
Changes in version 1.875, 2003-01-01:
allowed some non-error action other than a default reduction on the
error token. The new behavior has long been the documented behavior,
and has long been required by POSIX. For more details, please see
- <http://mail.gnu.org/pipermail/bug-bison/2002-May/001452.html>.
+ Paul Eggert, "Reductions during Bison error handling" (2002-05-20)
+ <http://lists.gnu.org/archive/html/bug-bison/2002-05/msg00038.html>.
* Traces
Popped tokens and nonterminals are now reported.
-----
-Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004
+Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
Free Software Foundation, Inc.
This file is part of Bison, the GNU Compiler Compiler.
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.
+the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
+Boston, MA 02110-1301, USA.
projects / bison.git / blobdiff