X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/e88dbdbf44053609d81107824e34833e53761de7..2a8d363aabf1373d410deb96f5d030ccfed367a6:/NEWS?ds=sidebyside

diff --git a/NEWS b/NEWS
index 80c0b1f6..b6ab6934 100644
--- a/NEWS
+++ b/NEWS
@@ -1,10 +1,53 @@
 Bison News
 ----------
 
-Changes in version 1.49d:
+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.
 
-Changes in version 1.49b, 2002-08-12:
+* %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:
 
 * GLR parsing
   The declaration
@@ -14,6 +57,9 @@ Changes in version 1.49b, 2002-08-12:
   %dprec and %merge on grammar rules allow parse-time resolution of
   ambiguities.  Contributed by Paul Hilfinger.
 
+  Unfortunately Bison 1.50 does not work properly on 64-bit hosts
+  like the Alpha, so please stick to 32-bit hosts for now.
+
 * Output Directory
   When not in Yacc compatibility mode, when the output file was not
   specified, running `bison foo/bar.y' created `foo/bar.c'.  It
@@ -155,7 +201,6 @@ Changes in version 1.35, 2002-03-25:
 
   This kludge also addresses some C++ problems when the stack was
   extended.
-
 
 Changes in version 1.34, 2002-03-12: