bison: avoid warnings from static code analysis

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 490e89ed5c9cbe1ae340d45b924c62da22c587a8..18771946493ee66703770dfc06b5e8daec59a5ff 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -4,19 +4,23 @@ GNU Bison NEWS
 
 ** Bug fixes
 
 
 ** Bug fixes
 

-*** Named %union support
+*** C++ with Variants (lalr1.cc)
+
+  Problems with %destructor and '%define parse.assert' have been fixed.
+
+*** Named %union support (yacc.c, glr.c)

 
   Bison 3.0 introduced a regression on named %union such as
 
     %union foo { int ival; };
 
 
   Bison 3.0 introduced a regression on named %union such as
 
     %union foo { int ival; };
 

-  The possibility to use a name was introduced ``for Yacc compatibility''.
+  The possibility to use a name was introduced "for Yacc compatibility".

   It is however not required by POSIX Yacc, and its usefulness is not clear.
 
   It is however not required by POSIX Yacc, and its usefulness is not clear.
 

-*** %define api.value.type union with %defines
+*** %define api.value.type union with %defines (yacc.c, glr.c)

 
 

-  The yacc.c and glr.c parsers were broken when %defines was used
-  together with "%define api.value.type union".
+  The C parsers were broken when %defines was used together with "%define
+  api.value.type union".

 
 *** Redeclarations are reported in proper order
 
 
 *** Redeclarations are reported in proper order