4 Changes in version 1.49a:
9 * The initial rule is explicit.
10 Bison used to play hacks with the initial rule, which the user does
11 not write. It is now explicit, and visible in the reports and
14 * Useless rules are actually removed.
15 Before, Bison reported the useless rules, but, although not used,
16 included them in the parsers.
18 * False `Token not used' report fixed.
23 exp: '0' %prec useful;
25 where a token was used to set the precedence of the last rule,
26 bison reported both `useful' and `useless' as useless tokens.
28 * Revert the C++ namespace changes introduced in 1.31, as they caused too
29 many portability hassles.
32 Bison no longer dumps core when there are too many items, it just
36 The token end of file may be specified by the user, in which case,
37 the user symbol is used in the reports, the graphs, and the verbose
38 error messages instead of `$', which remains being the defaults.
42 %token YYEOF 0 "end of file"
44 Changes in version 1.31, 2002-01-14:
48 * GNU Gettext and %expect
49 GNU Gettext asserts 10 s/r conflicts, but there are 7. Now that
50 Bison dies on incorrect %expectations, we fear there will be
51 too many bug reports for Gettext, so _for the time being_, %expect
52 does not trigger an error when the input file is named `plural.y'.
54 * Use of alloca in parsers
55 If YYSTACK_USE_ALLOCA is defined to 0, then the parsers will use
56 malloc exclusively. Since 1.29, but was not NEWS'ed.
58 alloca is used only when compiled with GCC, to avoid portability
61 * When the generated parser lacks debugging code, YYDEBUG is now 0
62 (as POSIX requires) instead of being undefined.
65 Bison has always permitted actions such as { $$ = $1 }: it adds the
66 ending semicolon. Now if in Yacc compatibility mode, the semicolon
67 is no longer output: one has to write { $$ = $1; }.
69 * Better C++ compliance
70 The output parsers try to respect C++ namespaces.
73 Fixed bugs when reporting useless nonterminals.
76 The parsers work properly on 64 bit hosts.
79 Some calls to strerror resulted in scrambled or missing error messages.
82 When the number of shift/reduce conflicts is correct, don't issue
85 * The verbose report includes the rule line numbers.
87 * Rule line numbers are fixed in traces.
92 Verbose parse error messages from the parsers are better looking.
93 Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'(''
94 Now: parse error: unexpected '/', expecting "number" or '-' or '('
96 * Fixed parser memory leaks.
97 When the generated parser was using malloc to extend its stacks, the
98 previous allocations were not freed.
100 * Fixed verbose output file.
101 Some newlines were missing.
102 Some conflicts in state descriptions were missing.
104 * Fixed conflict report.
105 Option -v was needed to get the result.
109 Mismatches are errors, not warnings.
111 * Fixed incorrect processing of some invalid input.
113 * Fixed CPP guards: 9foo.h uses BISON_9FOO_H instead of 9FOO_H.
115 * Fixed some typos in the documentation.
117 * %token MY_EOF 0 is supported.
118 Before, MY_EOF was silently renumbered as 257.
120 * doc/refcard.tex is updated.
122 * %output, %file-prefix, %name-prefix.
126 New, aliasing `--output-file'.
128 Changes in version 1.30:
130 * `--defines' and `--graph' have now an optionnal argument which is the
131 output file name. `-d' and `-g' do not change, they do not take any
134 * `%source_extension' and `%header_extension' are removed, failed
139 Changes in version 1.29, 2001-09-07:
141 * The output file does not define const, as this caused problems when used
142 with common autoconfiguration schemes. If you still use ancient compilers
143 that lack const, compile with the equivalent of the C compiler option
144 `-Dconst='. autoconf's AC_C_CONST macro provides one way to do this.
146 * Added `-g' and `--graph'.
148 * The Bison manual is now distributed under the terms of the GNU FDL.
150 * The input and the output files has automatically a similar extension.
152 * Russian translation added.
154 * NLS support updated; should hopefully be less troublesome.
156 * Added the old Bison reference card.
158 * Added `--locations' and `%locations'.
160 * Added `-S' and `--skeleton'.
162 * `%raw', `-r', `--raw' is disabled.
164 * Special characters are escaped when output. This solves the problems
165 of the #line lines with path names including backslashes.
168 `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose',
169 `%debug', `%source_extension' and `%header_extension'.
172 Automatic location tracking.
174 Changes in version 1.28, 1999-07-06:
176 * Should compile better now with K&R compilers.
180 * Fixed a problem with escaping the double quote character.
182 * There is now a FAQ.
184 Changes in version 1.27:
186 * The make rule which prevented bison.simple from being created on
187 some systems has been fixed.
189 Changes in version 1.26:
191 * Bison now uses automake.
193 * New mailing lists: <bug-bison@gnu.org> and <help-bison@gnu.org>.
195 * Token numbers now start at 257 as previously documented, not 258.
197 * Bison honors the TMPDIR environment variable.
199 * A couple of buffer overruns have been fixed.
201 * Problems when closing files should now be reported.
203 * Generated parsers should now work even on operating systems which do
204 not provide alloca().
206 Changes in version 1.25, 1995-10-16:
208 * Errors in the input grammar are not fatal; Bison keeps reading
209 the grammar file, and reports all the errors found in it.
211 * Tokens can now be specified as multiple-character strings: for
212 example, you could use "<=" for a token which looks like <=, instead
213 of chosing a name like LESSEQ.
215 * The %token_table declaration says to write a table of tokens (names
216 and numbers) into the parser file. The yylex function can use this
217 table to recognize multiple-character string tokens, or for other
220 * The %no_lines declaration says not to generate any #line preprocessor
221 directives in the parser file.
223 * The %raw declaration says to use internal Bison token numbers, not
224 Yacc-compatible token numbers, when token names are defined as macros.
226 * The --no-parser option produces the parser tables without including
227 the parser engine; a project can now use its own parser engine.
228 The actions go into a separate file called NAME.act, in the form of
229 a switch statement body.
231 Changes in version 1.23:
233 The user can define YYPARSE_PARAM as the name of an argument to be
234 passed into yyparse. The argument should have type void *. It should
235 actually point to an object. Grammar actions can access the variable
236 by casting it to the proper pointer type.
238 Line numbers in output file corrected.
240 Changes in version 1.22:
244 Changes in version 1.20:
246 Output file does not redefine const for C++.