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 135. Here are the URLs for the gzip and bzip2 compressed tar images: ftp://ftp.gnu.org/gnu/bison/bison-2.1.tar.gz ftp://ftp.gnu.org/gnu/bison/bison-2.1.tar.bz2 Here is the MD5 checksum: b1468d49c1357aebcd1de6ef12cbf3e8 bison-2.1.tar.gz ef3110077462b1140b2ae612626e8486 bison-2.1.tar.bz2 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 - cd bison-2.1 ./configure make make check # Ignore problems with test 135 "Duplicated user destructor for lookahead". We particularly appreciate tests on unusual hosts. Please report bugs to <bug-bison@gnu.org>. 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, unexpected "number"'. _______________________________________________ GNU Announcement mailing list <info-gnu@gnu.org> http://lists.gnu.org/mailman/listinfo/info-gnu
