[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bison 2.1 released
Bison 2.1 released
Mon, 19 Sep 2005 13:03:30 -0700
Bison version 2.1 has been released.
Bison is a parser generator that is compatible with Yacc.
Please see <http://www.gnu.org/software/bison/> for more info.
Bison 2.1 is mostly a bug fix version since the last official release
of Bison. Last-minute testing uncovered one possible problem in the
Bison self-test suite. The last test case (test 135, Duplicated user
destructor for lookahead) may fail if you are using older versions of
GCC. This is a bug in the test case, not a bug in Bison itself, so
please don't worry about it if "make check" reports a failure for test
Here are the URLs for the gzip and bzip2 compressed tar images:
Here is the MD5 checksum:
This version is byte-for-byte identical to the test version that was
prereleased on alpha.gnu.org, so if you have that version you don't
need to get the new one.
To try this version, please make sure you have GNU m4 1.4.3 installed.
Then obtain the file bison-2.1.tar.gz, and execute the following shell
commands or their equivalents:
gunzip <bison-2.1.tar.gz | tar xf -
# Ignore problems with test 135 "Duplicated user destructor for lookahead".
We particularly appreciate tests on unusual hosts.
Please report bugs to <address@hidden>.
Here is a list of user-visible changes in version 2.1.
* Bison-generated parsers now support the translation of diagnostics like
"syntax error" into languages other than English. The default
language is still English. For details, please see the new
Internationalization section of the Bison manual. Software
distributors should also see the new PACKAGING file. Thanks to
Bruno Haible for this new feature.
* Wording in the Bison-generated parsers has been changed slightly to
simplify translation. In particular, the message "memory exhausted"
has replaced "parser stack overflow", as the old message was not
always accurate for modern Bison-generated parsers.
* Destructors are now called when the parser aborts, for all symbols left
behind on the stack. Also, the start symbol is now destroyed after a
successful parse. In both cases, the behavior was formerly inconsistent.
* When generating verbose diagnostics, Bison-generated 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,
|[Prev in Thread]
||[Next in Thread]|
- Bison 2.1 released,
Paul Eggert <=