(struniq_assert): Now returns void, and aborts if the assertion is false.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 1bf3b70dc149a86583ea3a830f02aee36d10b7f7..554f32caa82368e8a3cda3f3630f058acd2a8fd0 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,14 +1,28 @@
 Bison News
 ----------
+Changes in version 1.75c:
 
-Changes in version 1.75b:
+* "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 digraphs, UCNs, and
-  backslash-newline within C escape sequences, as POSIX now requires.
+* 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.
 
@@ -164,9 +178,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.