X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/959e5f515a22942a4910ada629ee98540d90d940..e19c4e5d1c72a11ab2abba8ee51170f575ded43b:/NEWS diff --git a/NEWS b/NEWS index c61394b7..1a1310b0 100644 --- a/NEWS +++ b/NEWS @@ -1,10 +1,39 @@ Bison News ---------- -Changes in version 1.75b: +Changes in version 1.75d: -* Bison now parses C99 lexical constructs like digraphs, UCNs, and - backslash-newline within C escape sequences, as POSIX now requires. +* Yacc library now available + 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. + +* %lex-param, %parse-param + These now take just one operand, not two. + +Changes in version 1.75c, 2002-11-25: + +* "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. + +* "parsing stack overflow..." -> "parser stack overflow" + GLR parsers now report "parser stack overflow" as per the Bison manual. + +* GLR and inline + Users of Bison have to decide how they handle the portability of the + C keyword `inline'. + +Changes in version 1.75b, 2002-11-13: + +* %destructor + It is now possible to reclaim the memory associated to symbols + discarded during error recovery. This feature is still experimental. + +* Bison now parses C99 lexical constructs like UCNs and + backslash-newline within C escape sequences, as POSIX 1003.1-2001 requires. * --no-line works properly. @@ -160,9 +189,9 @@ Changes in version 1.50, 2002-10-04: the user symbol is used in the reports, the graphs, and the verbose 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.