Bison now parses C99 lexical constructs like digraphs, UCNs, and

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 14fc787fef24a64a42174479591a260d70de2bfa..bfc31882f4e22829022939a62917117f1b3b8022 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,56 @@
 Bison News
 ----------
 
-Changes in version 1.50a:
+Changes in version 1.75b:
+
+* Bison now parses C99 lexical constructs like digraphs, UCNs, and
+  backslash-newline within C escape sequences, as POSIX now requires.
+
+Changes in version 1.75a, 2002-10-24:
+
+* Bison can no longer be built by a K&R C compiler; it requires C89 or
+  later to be built.  This change originally took place a few versions
+  ago, but nobody noticed until we recently asked someone to try
+  building Bison with a K&R C compiler.
+
+* %error-verbose
+  This new directive is preferred over YYERROR_VERBOSE.
+
+* %lex-param, %parse-param
+  These new directives are preferred over PARSE_PARAM and LEX_PARAM.
+  In addition, they provide a means for yyerror to remain pure, and
+  to access to the current location.
+
+Changes in version 1.75, 2002-10-14:
 
 * Bison should now work on 64-bit hosts.
 
+* Indonesian translation thanks to Tedi Heriyanto.
+
+* GLR parsers
+  Fix spurious parse errors.
+
+* Pure parsers
+  Some people redefine yyerror to steal yyparse' private variables.
+  Reenable this trick until an official feature replaces it.
+
+* Type Clashes
+  In agreement with POSIX and with other Yaccs, leaving a default
+  action is valid when $$ is untyped, and $1 typed:
+
+       untyped: ... typed;
+
+  but the converse remains an error:
+
+       typed: ... untyped;
+
+* Values of mid-rule actions
+  The following code:
+
+       foo: { ... } { $$ = $1; } ...
+
+  was incorrectly rejected: $1 is defined in the second mid-rule
+  action, and is equal to the $$ of the first mid-rule action.
 
 Changes in version 1.50, 2002-10-04: