Regenerate.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 4de67f10adceccd560b6d9499f275b2172ea48ad..54775985a887aa22dbd47d85396fc2b3ea7c168d 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,14 +1,16 @@
 Bison News
 ----------
 
 Bison News
 ----------
 

-Changes in version 2.1b:
+Changes in version 2.2, 2006-05-19:
+
+* The distribution terms for all Bison-generated parsers now permit
+  using the parsers in nonfree programs.  Previously, this permission
+  was granted only for Bison-generated LALR(1) parsers in C.

 
 * %name-prefix changes the namespace name in C++ outputs.
 
 * The C++ parsers export their token_type.
 
 
 * %name-prefix changes the namespace name in C++ outputs.
 
 * The C++ parsers export their token_type.
 

-Changes in version 2.1a, 2006-02-13:
-

 * Bison now allows multiple %union declarations, and concatenates
   their contents together.
 
 * Bison now allows multiple %union declarations, and concatenates
   their contents together.
 


@@ -77,10 +79,10 @@ Changes in version 2.1a, 2006-02-13:
   for previous releases of Bison, and this one.
 
   If you wish to update, then make sure older version of Bison will
   for previous releases of Bison, and this one.
 
   If you wish to update, then make sure older version of Bison will

-  fail using `%require "2.1a"'.
+  fail using `%require "2.2"'.

 
 * DJGPP support added.
 
 * DJGPP support added.

-
+\f

 Changes in version 2.1, 2005-09-16:
 
 * The C++ lalr1.cc skeleton supports %lex-param.
 Changes in version 2.1, 2005-09-16:
 
 * The C++ lalr1.cc skeleton supports %lex-param.


@@ -106,7 +108,7 @@ Changes in version 2.1, 2005-09-16:
   a syntax error associated with '%token NUM "number"' they might
   print 'syntax error, unexpected number' instead of 'syntax error,
   unexpected "number"'.
   a syntax error associated with '%token NUM "number"' they might
   print 'syntax error, unexpected number' instead of 'syntax error,
   unexpected "number"'.

-
+\f

 Changes in version 2.0, 2004-12-25:
 
 * Possibly-incompatible changes
 Changes in version 2.0, 2004-12-25:
 
 * Possibly-incompatible changes