* doc/bison.texinfo: Correct typos in previous fix.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 272168f2c2403d2432db8ecec5382cf4ed2b630f..8593f27ff1e14f2653ed79ab8d0adbd21a54d33a 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,17 +1,30 @@
 Bison News
 ----------
 
 Bison News
 ----------
 

-Changes in the next version (not yet released):
+Changes in version 2.0b, 2005-07-24:

 
 

-* Bison-generated C parsers now support the translation of diagnostics like
+* 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
   "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.  Thanks to Bruno
-  Haible for this new feature.
+  Internationalization section of the Bison manual.  Software
+  distributors should also see the new PACKAGING file.  Thanks to
+  Bruno Haible for this new feature.

 
 

-The following change was also in version 2.0a, 2005-05-22:
+* 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.

 
 

-* When generating verbose diagnostics, Bison-generated C parsers no longer
+* 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,
   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,