X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/fdac0091ce81d8b374488d24f2fcebde045bc333..353d3eb65130304744b0ea1a4a317517eec7b956:/NEWS

diff --git a/NEWS b/NEWS
index 98d4f939..1a1310b0 100644
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,39 @@
 Bison News
 ----------
 
-Changes in version 1.75b:
+Changes in version 1.75d:
 
-* Bison now parses C99 lexical constructs like digraphs, UCNs, and
-  backslash-newline within C escape sequences, as POSIX now requires.
+* Yacc library now available
+  Bison now installs a small library liby.a containing implementations
+  of Yacc-compatible yyerror and main functions.  This library is
+  normally not useful, but POSIX requires it.
+
+* %lex-param, %parse-param
+  These now take just one operand, not two.
+
+Changes in version 1.75c, 2002-11-25:
+
+* "parse error" -> "syntax error"
+  Bison now uniformly uses the term "syntax error"; formerly, the code
+  and manual sometimes used the term "parse error" instead.  POSIX
+  requires "syntax error" in diagnostics, and it was thought better to
+  be consistent.
+
+* "parsing stack overflow..." -> "parser stack overflow"
+  GLR parsers now report "parser stack overflow" as per the Bison manual.
+
+* GLR and inline
+  Users of Bison have to decide how they handle the portability of the
+  C keyword `inline'.
+
+Changes in version 1.75b, 2002-11-13:
+
+* %destructor
+  It is now possible to reclaim the memory associated to symbols
+  discarded during error recovery.  This feature is still experimental.
+
+* Bison now parses C99 lexical constructs like UCNs and
+  backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires.
 
 * --no-line works properly.
 
@@ -16,6 +45,9 @@ Changes in version 1.75b:
   In addition, they provide a means for yyerror to remain pure, and
   to access to the current location.
 
+  #defining yyerror to steal internal variables is strongly
+  discouraged.  It is not guaranteed to work for ever.
+
 * #line
   Bison now recognizes #line in its input, and forwards them.
 
@@ -157,9 +189,9 @@ Changes in version 1.50, 2002-10-04:
   the user symbol is used in the reports, the graphs, and the verbose
   error messages instead of `$end', which remains being the default.
   For instance
-     %token YYEOF 0
+     %token MYEOF 0
   or
-     %token YYEOF 0 "end of file"
+     %token MYEOF 0 "end of file"
 
 * Semantic parser
   This old option, which has been broken for ages, is removed.