(Error Reporting): randomness -> nastiness, to fix a typo.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 022aa47fd3b9b922f7637188640a230dd4d5374a..3f546c8f42553d43d40b3bbcdecce2e04476d41d 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,52 @@
 Bison News
 ----------
 
-Changes in version 1.75b:
+Changes in version 1.75d, 2002-12-13:
 
-* Bison now parses C99 lexical constructs like digraphs, UCNs, and
-  backslash-newline within C escape sequences, as POSIX now requires.
+* Semicolons are once again optional at the end of grammar rules.
+  This reverts to the behavior of Bison 1.33 and earlier, and improves
+  compatibility with Yacc.
+
+* Type clashes now generate warnings, not errors.
+
+* Yacc command and library now available
+  The Bison distribution now installs a yacc command, as POSIX requires.
+  Also, 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.
+
+* The documentation now emphasizes that yylex and yyerror must be
+  declared before use.  C99 requires this.
+
+* The documentation license has been upgraded to version 1.2
+  of the GNU Free Documentation License.
+
+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 +58,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 +202,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.
@@ -339,8 +384,8 @@ Changes in version 1.31, 2002-01-14:
 \f
 Changes in version 1.30, 2001-10-26:
 
-* `--defines' and `--graph' have now an optionnal argument which is the
-  output file name. `-d' and `-g' do not change, they do not take any
+* `--defines' and `--graph' have now an optional argument which is the
+  output file name. `-d' and `-g' do not change; they do not take any
   argument.
 
 * `%source_extension' and `%header_extension' are removed, failed