X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/8c165d891d5db7953b90142ed34cbbbc114e7f67..006d217ddd94818a6b6501db2344647fadea5bf4:/NEWS diff --git a/NEWS b/NEWS index 8eeef044..5c5e8c41 100644 --- a/NEWS +++ b/NEWS @@ -1,27 +1,192 @@ Bison News ---------- -Changes in version 1.49b: +Changes in version 1.875c: + +Changes in version 1.875b, 2003-06-17: + +* GLR grammars now support locations. + +* Semicolon changes: + - Semicolons are now allowed before "|" in grammar rules, as POSIX requires. + - Stray semicolons are no longer allowed at the start of a grammar. + - Semicolons are now required after in-grammar declarations. + +Changes in version 1.875a, 2003-02-01: + +* 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. + +* New configure option --disable-yacc, to disable installation of the + yacc command and -ly library introduced in 1.875 for POSIX conformance. + +Changes in version 1.875, 2003-01-01: + +* The documentation license has been upgraded to version 1.2 + of the GNU Free Documentation License. + +* syntax error processing + + - In Yacc-style parsers YYLLOC_DEFAULT is now used to compute error + locations too. This fixes bugs in error-location computation. + + - %destructor + It is now possible to reclaim the memory associated to symbols + discarded during error recovery. This feature is still experimental. + + - %error-verbose + This new directive is preferred over YYERROR_VERBOSE. + + - #defining yyerror to steal internal variables is discouraged. + It is not guaranteed to work forever. + +* POSIX conformance + + - 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. + + - `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. + + - The documentation now emphasizes that yylex and yyerror must be + declared before use. C99 requires this. + + - Bison now parses C99 lexical constructs like UCNs and + backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires. + + - File names are properly escaped in C output. E.g., foo\bar.y is + output as "foo\\bar.y". + + - 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. + + - Type clashes now generate warnings, not errors. + + - 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. + +* 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. + +Changes in version 1.75, 2002-10-14: + +* Bison should now work on 64-bit hosts. + +* Indonesian translation thanks to Tedi Heriyanto. + +* GLR parsers + Fix spurious parse errors. + +* Pure parsers + Some people redefine yyerror to steal yyparse' private variables. + Reenable this trick until an official feature replaces it. + +* Type Clashes + In agreement with POSIX and with other Yaccs, leaving a default + action is valid when $$ is untyped, and $1 typed: + + untyped: ... typed; + + but the converse remains an error: + + typed: ... untyped; + +* Values of mid-rule actions + The following code: + + foo: { ... } { $$ = $1; } ... + + was incorrectly rejected: $1 is defined in the second mid-rule + action, and is equal to the $$ of the first mid-rule action. + +Changes in version 1.50, 2002-10-04: + +* GLR parsing + The declaration + %glr-parser + causes Bison to produce a Generalized LR (GLR) parser, capable of handling + almost any context-free grammar, ambiguous or not. The new declarations + %dprec and %merge on grammar rules allow parse-time resolution of + ambiguities. Contributed by Paul Hilfinger. + + Unfortunately Bison 1.50 does not work properly on 64-bit hosts + like the Alpha, so please stick to 32-bit hosts for now. * Output Directory When not in Yacc compatibility mode, when the output file was not - specified, runnning `bison foo/bar.y' created `foo/bar.c'. It + specified, running `bison foo/bar.y' created `foo/bar.c'. It now creates `bar.c'. * Undefined token The undefined token was systematically mapped to 2 which prevented - the use of 2 from the user. This is no longer the case. + the use of 2 by the user. This is no longer the case. * Unknown token numbers - If yylex returned a code out of range, yyparse could die. This is + If yylex returned an out of range value, yyparse could die. This is no longer the case. * Error token - According to POSIX, the error token should be numbered as 256. + According to POSIX, the error token must be 256. Bison extends this requirement by making it a preference: *if* the user specified that one of her tokens is numbered 256, then error will be mapped onto another number. +* Verbose error messages + They no longer report `..., expecting error or...' for states where + error recovery is possible. + +* End token + Defaults to `$end' instead of `$'. + * Error recovery now conforms to documentation and to POSIX When a Bison-generated parser encounters a syntax error, it now pops the stack until it finds a state that allows shifting the error @@ -34,9 +199,11 @@ Changes in version 1.49b: * Traces Popped tokens and nonterminals are now reported. -* Large grammars - Large grammars are now supported (large token numbers, large grammar - size (= sum of the LHS and RHS lengths), large LALR tables). +* Larger grammars + Larger grammars are now supported (larger token numbers, larger grammar + size (= sum of the LHS and RHS lengths), larger LALR tables). + Formerly, many of these numbers ran afoul of 16-bit limits; + now these limits are 32 bits on most hosts. * Explicit initial rule Bison used to play hacks with the initial rule, which the user does @@ -50,6 +217,10 @@ Changes in version 1.49b: * Useless rules, useless nonterminals They are now reported, as a warning, with their locations. +* Rules never reduced + Rules that can never be reduced because of conflicts are now + reported. + * Incorrect `Token not used' On a grammar such as @@ -72,25 +243,26 @@ Changes in version 1.49b: * Token end-of-file The token end of file may be specified by the user, in which case, the user symbol is used in the reports, the graphs, and the verbose - error messages instead of `$', which remains being the defaults. + error messages instead of `$end', which remains being the default. For instance - %token YYEOF 0 + %token MYEOF 0 or - %token YYEOF 0 "end of file" + %token MYEOF 0 "end of file" * Semantic parser This old option, which has been broken for ages, is removed. -* New translation +* New translations + Brazilian Portuguese, thanks to Alexandre Folle de Menezes. Croatian, thanks to Denis Lackovic. * Incorrect token definitions - When fed with `%token 'a' "A"', Bison used to output `#define 'a' 65'. + When given `%token 'a' "A"', Bison used to output `#define 'a' 65'. * Token definitions as enums Tokens are output both as the traditional #define's, and, provided the compiler supports ANSI C or is a C++ compiler, as enums. - This helps debuggers producing symbols instead of values. + This lets debuggers display names instead of integers. * Reports In addition to --verbose, bison supports --report=THINGS, which @@ -113,6 +285,8 @@ Changes in version 1.49b: bar: '0' {} '0'; This is fixed. + +* GNU M4 is now required when using Bison. Changes in version 1.35, 2002-03-25: @@ -128,7 +302,6 @@ Changes in version 1.35, 2002-03-25: This kludge also addresses some C++ problems when the stack was extended. - Changes in version 1.34, 2002-03-12: @@ -254,8 +427,8 @@ Changes in version 1.31, 2002-01-14: Changes in version 1.30, 2001-10-26: -* `--defines' and `--graph' have now an optionnal argument which is the - output file name. `-d' and `-g' do not change, they do not take any +* `--defines' and `--graph' have now an optional argument which is the + output file name. `-d' and `-g' do not change; they do not take any argument. * `%source_extension' and `%header_extension' are removed, failed @@ -378,16 +551,17 @@ End: ----- -Copyright (C) 2001, 2002 Free Software Foundation, Inc. +Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 +Free Software Foundation, Inc. -This file is part of GNU Autoconf. +This file is part of Bison, the GNU Compiler Compiler. -GNU Autoconf is free software; you can redistribute it and/or modify +Bison is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. -GNU Autoconf is distributed in the hope that it will be useful, +Bison is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.