[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bison test version 2.0b available

From: Paul Eggert
Subject: Bison test version 2.0b available
Date: Tue, 26 Jul 2005 13:34:15 -0700
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

Bison test version 2.0b is now available.  It contains mostly bug
fixes for Bison 2.0.  Our intention is to generate a new official
release soon, based on feedback from this test version.

Here is the URL:


I've asked the GNU FTP upload gurus to copy it to here:


Here is the MD5 checksum:

47e84c977910be6e136ee6b4bf4967c7  bison-2.0b.tar.gz

To try this test version, please make sure you have GNU m4 1.4.3
<ftp://ftp.gnu.org/gnu/m4/m4-1.4.3.tar.gz> installed, and then execute
the following shell commands or their equivalents:

   wget http://www.cs.ucla.edu/~eggert/bison/bison-2.0b.tar.gz
   gunzip <bison-2.0b.tar.gz | tar xf -
   cd bison-2.0b
   make check

We particularly appreciate tests on unusual hosts.

Please report bugs to <address@hidden>.

Bison is a parser generator that is compatible with Yacc.
Please see <http://www.gnu.org/software/bison/> for more info about Bison.

Here is a list of user-visible changes since Bison 2.0:

Changes in version 2.0b, 2005-07-24:

* 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.

* The yytname array now contains the same contents that it did in 2.0,
  undoing an incompatible and undocumented change made in 2.0a.

Changes in version 2.0a, 2005-05-22:

* 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"'.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]