bison-patches
[Top][All Lists]
Advanced

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

Bison 2.1 candidate tarballs available


From: Paul Eggert
Subject: Bison 2.1 candidate tarballs available
Date: Fri, 16 Sep 2005 16:15:28 -0700
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

I made tarballs for Bison 2.1 and have copied them to the following
locations.  If there are no obvious installation gotchas with these, I
plan to install them at the official ftp.gnu.org location Monday.
Please let me know if you run into showstopper problems.  Thanks.

ftp://alpha.gnu.org/gnu/bison/bison-2.1.tar.gz
ftp://alpha.gnu.org/gnu/bison/bison-2.1.tar.bz2

Here are MD5 checksums:

b1468d49c1357aebcd1de6ef12cbf3e8  bison-2.1.tar.gz
ef3110077462b1140b2ae612626e8486  bison-2.1.tar.bz2

There are no major changes since the last test release.
Here are the major changes since Bison 2.0 (taken from the NEWS file):

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





reply via email to

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