Regenerate.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 0407aad5ab66fde651f19972293fae05dbafe02d..8593f27ff1e14f2653ed79ab8d0adbd21a54d33a 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,111 +1,192 @@
 Bison News
 ----------
 
 Bison News
 ----------
 

-Changes in version 1.75f, 2002-12-28:
+Changes in version 2.0b, 2005-07-24:

 
 

-* In Yacc-style parsers YYLLOC_DEFAULT is now used to compute error
-  locations too.  This fixes bugs in error-location computation.
+* Bison-generated parsers now support the translation of diagnostics like
+  "syntax error" into languages other than English.  The default
+  language is still English.  For details, please see the new
+  Internationalization section of the Bison manual.  Software
+  distributors should also see the new PACKAGING file.  Thanks to
+  Bruno Haible for this new feature.

 
 

-* Bison now uses a Yacc-style format for conflict reports, e.g.,
-  "conflicts: 2 shift/reduce, 1 reduce/reduce".
+* Wording in the Bison-generated parsers has been changed slightly to
+  simplify translation.  In particular, the message "memory exhausted"
+  has replaced "parser stack overflow", as the old message was not
+  always accurate for modern Bison-generated parsers.

 
 

-* Bison now warns if it detects conflicting outputs to the same file,
-  e.g., it generates a warning for "bison -d -o foo.h foo.y" since
-  that command outputs both code and header to foo.h.
+* Destructors are now called when the parser aborts, for all symbols left
+  behind on the stack.  Also, the start symbol is now destroyed after a
+  successful parse.  In both cases, the behavior was formerly inconsistent.
+
+* The yytname array now contains the same contents that it did in 2.0,
+  undoing an incompatible and undocumented change made in 2.0a.
+
+Changes in version 2.0a, 2005-05-22:
+
+* When generating verbose diagnostics, Bison-generated parsers no longer
+  quote the literal strings associated with tokens.  For example, for
+  a syntax error associated with '%token NUM "number"' they might
+  print 'syntax error, unexpected number' instead of 'syntax error,
+  unexpected "number"'.
+
+Changes in version 2.0, 2004-12-25:
+
+* Possibly-incompatible changes
+
+  - Bison-generated parsers no longer default to using the alloca function
+    (when available) to extend the parser stack, due to widespread
+    problems in unchecked stack-overflow detection.  You can "#define
+    YYSTACK_USE_ALLOCA 1" to require the use of alloca, but please read
+    the manual to determine safe values for YYMAXDEPTH in that case.

 
 

-Changes in version 1.75e, 2002-12-24:
+  - Error token location.
+    During error recovery, the location of the syntax error is updated
+    to cover the whole sequence covered by the error token: it includes
+    the shifted symbols thrown away during the first part of the error
+    recovery, and the lookahead rejected during the second part.

 
 

-* If the user does not define YYSTYPE as a macro, Bison now declares it
-  using typedef instead of defining it as a macro.  POSIX requires this.
-  For consistency, YYLTYPE is also declared instead of defined.
+  - Semicolon changes:
+    . Stray semicolons are no longer allowed at the start of a grammar.
+    . Semicolons are now required after in-grammar declarations.

 
 

-* %union directives can now have a tag before the `{', e.g., the
-  directive `%union foo {...}' now generates the C code
-  `typedef union foo { ... } YYSTYPE;'; this is for Yacc compatibility.
-  The default union tag is `YYSTYPE', for compatibility with Solaris 9 Yacc.
-  For consistency, YYLTYPE's struct tag is now `YYLTYPE' instead of `yyltype'.
+  - 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.

 
 

-* `yystype' and `yyltype' are now obsolescent macros instead of being
-  typedefs or tags; they are no longer documented and will be
-  withdrawn in a future release.
+  - NUL bytes are no longer allowed in Bison string literals, unfortunately.

 
 

-* References to the experimental %lex-param and %parse-param directives
-  have been temporarily removed from the manual, since we don't want
-  users to rely upon these features quite yet.
+* New features

 
 

-Changes in version 1.75d, 2002-12-13:
+  - GLR grammars now support locations.

 
 

-* Semicolons are once again optional at the end of grammar rules.
-  This reverts to the behavior of Bison 1.33 and earlier, and improves
-  compatibility with Yacc.
+  - New directive: %initial-action.
+    This directive allows the user to run arbitrary code (including
+    initializing @$) from yyparse before parsing starts.

 
 

-* Type clashes now generate warnings, not errors.
+  - A new directive "%expect-rr N" specifies the expected number of
+    reduce/reduce conflicts in GLR parsers.

 
 

-* Yacc command and library now available
-  The Bison distribution now installs a yacc command, as POSIX requires.
-  Also, Bison now installs a small library liby.a containing
-  implementations of Yacc-compatible yyerror and main functions.
-  This library is normally not useful, but POSIX requires it.
+  - %token numbers can now be hexadecimal integers, e.g., `%token FOO 0x12d'.
+    This is a GNU extension.

 
 

-* %lex-param, %parse-param
-  These now take just one operand, not two.
+  - The option `--report=lookahead' was changed to `--report=look-ahead'.
+    The old spelling still works, but is not documented and will be
+    removed.

 
 

-* The documentation now emphasizes that yylex and yyerror must be
-  declared before use.  C99 requires this.
+  - Experimental %destructor support has been added to lalr1.cc.
+
+  - New configure option --disable-yacc, to disable installation of the
+    yacc command and -ly library introduced in 1.875 for POSIX conformance.
+
+* Bug fixes
+
+  - For now, %expect-count violations are now just warnings, not errors.
+    This is for compatibility with Bison 1.75 and earlier (when there are
+    reduce/reduce conflicts) and with Bison 1.30 and earlier (when there
+    are too many or too few shift/reduce conflicts).  However, in future
+    versions of Bison we plan to improve the %expect machinery so that
+    these violations will become errors again.
+
+  - Within Bison itself, numbers (e.g., goto numbers) are no longer
+    arbitrarily limited to 16-bit counts.
+
+  - Semicolons are now allowed before "|" in grammar rules, as POSIX requires.
+\f
+Changes in version 1.875, 2003-01-01:

 
 * The documentation license has been upgraded to version 1.2
   of the GNU Free Documentation License.
 
 
 * The documentation license has been upgraded to version 1.2
   of the GNU Free Documentation License.
 

-Changes in version 1.75c, 2002-11-25:
+* syntax error processing
+
+  - In Yacc-style parsers YYLLOC_DEFAULT is now used to compute error
+    locations too.  This fixes bugs in error-location computation.

 
 

-* "parse error" -> "syntax error"
-  Bison now uniformly uses the term "syntax error"; formerly, the code
-  and manual sometimes used the term "parse error" instead.  POSIX
-  requires "syntax error" in diagnostics, and it was thought better to
-  be consistent.
+  - %destructor
+    It is now possible to reclaim the memory associated to symbols
+    discarded during error recovery.  This feature is still experimental.

 
 

-* "parsing stack overflow..." -> "parser stack overflow"
-  GLR parsers now report "parser stack overflow" as per the Bison manual.
+  - %error-verbose
+    This new directive is preferred over YYERROR_VERBOSE.

 
 

-* GLR and inline
-  Users of Bison have to decide how they handle the portability of the
-  C keyword `inline'.
+  - #defining yyerror to steal internal variables is discouraged.
+    It is not guaranteed to work forever.

 
 

-Changes in version 1.75b, 2002-11-13:
+* POSIX conformance

 
 

-* %destructor
-  It is now possible to reclaim the memory associated to symbols
-  discarded during error recovery.  This feature is still experimental.
+  - Semicolons are once again optional at the end of grammar rules.
+    This reverts to the behavior of Bison 1.33 and earlier, and improves
+    compatibility with Yacc.

 
 

-* Bison now parses C99 lexical constructs like UCNs and
-  backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires.
+  - `parse error' -> `syntax error'
+    Bison now uniformly uses the term `syntax error'; formerly, the code
+    and manual sometimes used the term `parse error' instead.  POSIX
+    requires `syntax error' in diagnostics, and it was thought better to
+    be consistent.

 
 

-* --no-line works properly.
+  - The documentation now emphasizes that yylex and yyerror must be
+    declared before use.  C99 requires this.

 
 

-* %error-verbose
-  This new directive is preferred over YYERROR_VERBOSE.
+  - Bison now parses C99 lexical constructs like UCNs and
+    backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires.

 
 

-* %lex-param, %parse-param
-  These new directives are preferred over PARSE_PARAM and LEX_PARAM.
-  In addition, they provide a means for yyerror to remain pure, and
-  to access to the current location.
+  - File names are properly escaped in C output.  E.g., foo\bar.y is
+    output as "foo\\bar.y".

 
 

-  #defining yyerror to steal internal variables is strongly
-  discouraged.  It is not guaranteed to work for ever.
+  - Yacc command and library now available
+    The Bison distribution now installs a `yacc' command, as POSIX requires.
+    Also, Bison now installs a small library liby.a containing
+    implementations of Yacc-compatible yyerror and main functions.
+    This library is normally not useful, but POSIX requires it.

 
 

-* #line
-  Bison now recognizes #line in its input, and forwards them.
+  - Type clashes now generate warnings, not errors.

 
 

-* #line
-  File names are properly escaped. E.g. foo\bar.y give #line 123 "foo\\bar.y".
+  - If the user does not define YYSTYPE as a macro, Bison now declares it
+    using typedef instead of defining it as a macro.
+    For consistency, YYLTYPE is also declared instead of defined.

 
 

-Changes in version 1.75a, 2002-10-24:
+* Other compatibility issues
+
+  - %union directives can now have a tag before the `{', e.g., the
+    directive `%union foo {...}' now generates the C code
+    `typedef union foo { ... } YYSTYPE;'; this is for Yacc compatibility.
+    The default union tag is `YYSTYPE', for compatibility with Solaris 9 Yacc.
+    For consistency, YYLTYPE's struct tag is now `YYLTYPE' not `yyltype'.
+    This is for compatibility with both Yacc and Bison 1.35.
+
+  - `;' is output before the terminating `}' of an action, for
+    compatibility with Bison 1.35.
+
+  - Bison now uses a Yacc-style format for conflict reports, e.g.,
+    `conflicts: 2 shift/reduce, 1 reduce/reduce'.
+
+  - `yystype' and `yyltype' are now obsolescent macros instead of being
+    typedefs or tags; they are no longer documented and are planned to be
+    withdrawn in a future release.
+
+* GLR parser notes
+
+  - GLR and inline
+    Users of Bison have to decide how they handle the portability of the
+    C keyword `inline'.
+
+  - `parsing stack overflow...' -> `parser stack overflow'
+    GLR parsers now report `parser stack overflow' as per the Bison manual.
+
+* Bison now warns if it detects conflicting outputs to the same file,
+  e.g., it generates a warning for `bison -d -o foo.h foo.y' since
+  that command outputs both code and header to foo.h.
+
+* #line in output files
+  - --no-line works properly.

 
 * Bison can no longer be built by a K&R C compiler; it requires C89 or
   later to be built.  This change originally took place a few versions
   ago, but nobody noticed until we recently asked someone to try
   building Bison with a K&R C compiler.
 
 * Bison can no longer be built by a K&R C compiler; it requires C89 or
   later to be built.  This change originally took place a few versions
   ago, but nobody noticed until we recently asked someone to try
   building Bison with a K&R C compiler.

-
+\f

 Changes in version 1.75, 2002-10-14:
 
 * Bison should now work on 64-bit hosts.
 Changes in version 1.75, 2002-10-14:
 
 * Bison should now work on 64-bit hosts.


@@ -136,7 +217,7 @@ Changes in version 1.75, 2002-10-14:
 
   was incorrectly rejected: $1 is defined in the second mid-rule
   action, and is equal to the $$ of the first mid-rule action.
 
   was incorrectly rejected: $1 is defined in the second mid-rule
   action, and is equal to the $$ of the first mid-rule action.

-
+\f

 Changes in version 1.50, 2002-10-04:
 
 * GLR parsing
 Changes in version 1.50, 2002-10-04:
 
 * GLR parsing


@@ -183,7 +264,8 @@ Changes in version 1.50, 2002-10-04:
   allowed some non-error action other than a default reduction on the
   error token.  The new behavior has long been the documented behavior,
   and has long been required by POSIX.  For more details, please see
   allowed some non-error action other than a default reduction on the
   error token.  The new behavior has long been the documented behavior,
   and has long been required by POSIX.  For more details, please see

-  <http://mail.gnu.org/pipermail/bug-bison/2002-May/001452.html>.
+  Paul Eggert, "Reductions during Bison error handling" (2002-05-20)
+  <http://lists.gnu.org/archive/html/bug-bison/2002-05/msg00038.html>.

 
 * Traces
   Popped tokens and nonterminals are now reported.
 
 * Traces
   Popped tokens and nonterminals are now reported.


@@ -258,8 +340,8 @@ Changes in version 1.50, 2002-10-04:
   produces additional information:
   - itemset
     complete the core item sets with their closure
   produces additional information:
   - itemset
     complete the core item sets with their closure

-  - lookahead
-    explicitly associate lookaheads to items
+  - lookahead [changed to `look-ahead' in 1.875e and later]
+    explicitly associate look-ahead tokens to items

   - solved
     describe shift/reduce conflicts solving.
     Bison used to systematically output this information on top of
   - solved
     describe shift/reduce conflicts solving.
     Bison used to systematically output this information on top of


@@ -540,8 +622,8 @@ End:
 
 -----
 
 
 -----
 

-Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free
-Software Foundation, Inc.
+Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
+Free Software Foundation, Inc.

 
 This file is part of Bison, the GNU Compiler Compiler.
 
 
 This file is part of Bison, the GNU Compiler Compiler.
 


@@ -557,5 +639,5 @@ GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
 along with autoconf; see the file COPYING.  If not, write to
 
 You should have received a copy of the GNU General Public License
 along with autoconf; see the file COPYING.  If not, write to

-the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
-Boston, MA 02111-1307, USA.
+the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
+Boston, MA 02110-1301, USA.