Bison News
----------
+Changes in version 1.75c:
-Changes in version 1.75b:
+* "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.
-* Bison now parses C99 lexical constructs like digraphs, UCNs, and
- backslash-newline within C escape sequences, as POSIX now requires.
+* "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.
In addition, they provide a means for yyerror to remain pure, and
to access to the current location.
+ #defining yyerror to steal internal variables is strongly
+ discouraged. It is not guaranteed to work for ever.
+
* #line
Bison now recognizes #line in its input, and forwards them.
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.