X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/1452af69b4f4d2aeabf50918e9b6039cc809b988..13c29075c575899f3d1f41b5a65d13d589ee3dd1:/NEWS

diff --git a/NEWS b/NEWS
index 0d527484..36c20426 100644
--- a/NEWS
+++ b/NEWS
@@ -1,13 +1,30 @@
 Bison News
 ----------
 
-Changes in version 1.875d:
+Changes in version 1.875e:
+
+* New directive: %initial-action.
+  This directive allows the user to run arbitrary code (including
+  initializing @$) from yyparse before parsing starts.
+
+* The option `--report=lookahead' was changed to `--report=look-ahead'.
+  The old spelling still works, but is not documented and will be removed.
+
+Changes in version 1.875d, 2004-05-21:
+
+* Unescaped newlines are no longer allowed in character constants or
+  string literals.  They were never portable, and GCC 3.4.0 has
+  dropped support for them.  Better diagnostics are now generated if
+  forget a closing quote.
 
 * NUL bytes are no longer allowed in Bison string literals, unfortunately.
 
 * %token numbers can now be hexadecimal integers, e.g., `%token FOO 0x12d'.
   This is a GNU extension.
 
+* A new directive "%expect-rr N" specifies the expected number of
+  reduce/reduce conflicts in GLR parsers.
+
 * Experimental %destructor support has been added to lalr1.cc.
 
 Changes in version 1.875c, 2003-08-25:
@@ -280,8 +297,8 @@ Changes in version 1.50, 2002-10-04:
   produces additional information:
   - itemset
     complete the core item sets with their closure
-  - lookahead
-    explicitly associate lookaheads to items
+  - lookahead [changed to `look-ahead' in 1.875e and later]
+    explicitly associate look-ahead tokens to items
   - solved
     describe shift/reduce conflicts solving.
     Bison used to systematically output this information on top of