Document that undefined %prec identifier warnings will remain.

* NEWS (2.4.3): Here.
(2.4.2): Here.
(cherry picked from commit ff1f7871df81d5183eafeff380104da7a4a94749)

diff --git a/ChangeLog b/ChangeLog
index 5f7e63bcb793505a916b78e4e5008b742e46a302..567253730878ee52072c78b42a6171415476bddf 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2010-04-30  Joel E. Denny  <joeldenny@joeldenny.org>
+
+       Document that undefined %prec identifier warnings will remain.
+       * NEWS (2.4.3): Here.
+       (2.4.2): Here.
+
 2010-04-30  Joel E. Denny  <joeldenny@joeldenny.org>
 
        Revert 2009-12-30 change for undefined %prec token complaints.

diff --git a/NEWS b/NEWS
index b2e9e7c6d11e5ba44d295bd630c6d8fec64bc0b3..93312ff953a67d8f26464dc20a0f4e7a9ec15295 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -190,6 +190,11 @@ Bison News
 ** Failures in the test suite for some versions of Sun Studio C++ have
    been fixed.
 
+** Contrary to Bison 2.4.2's NEWS entry, it has been decided that
+   warnings about undefined %prec identifiers will not be converted to
+   errors in Bison 2.5.  They will remain warnings, which should be
+   sufficient for POSIX while avoiding backward compatibility issues.
+
 * Changes in version 2.4.2 (2010-03-20):
 
 ** Some portability problems that resulted in failures and livelocks
@@ -207,6 +212,8 @@ Bison News
   %prec directive.  It is now restored.  However, for backward
   compatibility with recent Bison releases, it is only a warning for
   now.  In Bison 2.5 and later, it will return to being an error.
+  [Between the 2.4.2 and 2.4.3 releases, it was decided that this
+  warning will not be converted to an error in Bison 2.5.]
 
 ** Detection of GNU M4 1.4.6 or newer during configure is improved.