(yyreturn): Don't pop stack if yyinitStateSet failed,

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index df296794485cbfc0a7b745d5f119e3b3fab23e83..ac3587ebf4a0fcda0dfeda0a7c43c57e50379afd 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,15 +1,27 @@
 Bison News
 ----------
 
 Bison News
 ----------
 

-Changes in version 2.0a, 2005-05-22:
+Changes in the next version (not yet released):

 
 

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

 
 

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