Reject unescaped newlines in strings.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 0d52748466f92970ae5e3b09775206e43685ad4e..a2c7e5a14489bbda31c67c3f6e87e43aa3a92081 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -3,11 +3,19 @@ Bison News
 
 Changes in version 1.875d:
 
 
 Changes in version 1.875d:
 

+* 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.
 
 * 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:
 * Experimental %destructor support has been added to lalr1.cc.
 
 Changes in version 1.875c, 2003-08-25: