* data/glr.c (yyresolveLocations): Remove bogus YYASSERT that the

[bison.git] / NEWS

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

-Changes in version 2.1a:
+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.

 
 * Bison now allows multiple %union declarations, and concatenates
   their contents together.
 
 * New warning: unused values
 
 * Bison now allows multiple %union declarations, and concatenates
   their contents together.
 
 * New warning: unused values

-  Typed right-hand side symbols whose value are not used are reported.
-  For instance:
+  Right-hand side symbols whose values are not used are reported,
+  if the symbols have destructors.  For instance:

 
      exp: exp "?" exp ":" exp { $1 ? $1 : $3; }
        | exp "+" exp
 
      exp: exp "?" exp ":" exp { $1 ? $1 : $3; }
        | exp "+" exp


@@ -16,14 +24,17 @@ Changes in version 2.1a:
 
   will trigger a warning about $$ and $5 in the first rule, and $3 in
   the second ($1 is copied to $$ by the default rule).  This example
 
   will trigger a warning about $$ and $5 in the first rule, and $3 in
   the second ($1 is copied to $$ by the default rule).  This example

-  most likely contains three errors, and should be rewritten as:
+  most likely contains three errors, and could be rewritten as:

 
 

-     exp: exp "?" exp ":" exp { $$ = $1 ? $3 : $5; }
-       | exp "+" exp         { $$ = $1 + $3; }
+     exp: exp "?" exp ":" exp
+           { $$ = $1 ? $3 : $5; free ($1 ? $5 : $3); free ($1); }
+       | exp "+" exp
+           { $$ = $1 ? $1 : $3; if ($1) free ($3); }

        ;
 
        ;
 

-  However, if the original actions were really intended, the warnings
-  can be suppressed by letting Bison believe the values are used, e.g.:
+  However, if the original actions were really intended, memory leaks
+  and all, the warnings can be suppressed by letting Bison believe the
+  values are used, e.g.:

 
      exp: exp "?" exp ":" exp { $1 ? $1 : $3; (void) ($$, $5); }
        | exp "+" exp         { $$ = $1; (void) $3; }
 
      exp: exp "?" exp ":" exp { $1 ? $1 : $3; (void) ($$, $5); }
        | exp "+" exp         { $$ = $1; (void) $3; }


@@ -34,12 +45,6 @@ Changes in version 2.1a:
 
      exp: exp { push ($1); } '+' exp { push ($3); sum (); };
 
 
      exp: exp { push ($1); } '+' exp { push ($3); sum (); };
 

-  Mid-rule actions that use $$ cause the corresponding value to be
-  set, therefore the following action must use it.  The following rule
-  triggers a warning about $2.
-
-     exp: '1' { $$ = 1; } '+' exp { $$ = $1 + $4; };
-

   The warning is intended to help catching lost values and memory leaks.
   If a value is ignored, its associated memory typically is not reclaimed.
 
   The warning is intended to help catching lost values and memory leaks.
   If a value is ignored, its associated memory typically is not reclaimed.
 


@@ -53,14 +58,14 @@ Changes in version 2.1a:
   instead of warnings.
 
 * GLR, YACC parsers.
   instead of warnings.
 
 * GLR, YACC parsers.

-  The %parse-params are available in the %destructor's (and the
-  experimental %printer's) as per the documentation.
+  The %parse-params are available in the destructors (and the
+  experimental printers) as per the documentation.

 
 * Bison now warns if it finds a stray `$' or `@' in an action.
 
 * %require "VERSION"
 
 * Bison now warns if it finds a stray `$' or `@' in an action.
 
 * %require "VERSION"

-  To specify that the grammar file depends on features implemented in
-  Bison version VERSION or higher.
+  This specifies that the grammar file depends on features implemented
+  in Bison version VERSION or higher.

 
 * lalr1.cc: The token and value types are now class members.
   The tokens were defined as free form enums and cpp macros.  YYSTYPE
 
 * lalr1.cc: The token and value types are now class members.
   The tokens were defined as free form enums and cpp macros.  YYSTYPE


@@ -74,10 +79,10 @@ Changes in version 2.1a:
   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.


@@ -103,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