4 Changes in version 1.30d:
9 Verbose parse error messages from the parsers are better looking.
10 Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'(''
11 Now: parse error: unexpected '/', expecting "number" or '-' or '('
14 Was broken when strings aliases for symbols were used.
16 Changes in version 1.30c:
18 * Fixed a few warnings.
20 * Some portability issues.
22 Changes in version 1.30b:
24 * Fixed parser memory leaks.
25 When the generated parser was using malloc to extend its stacks, the
26 previous allocations were not freed.
28 * Fixed verbose output file.
29 Some newlines were missing.
30 Some conflicts in state descriptions were missing.
32 * Fixed conflict report.
33 Option -v was needed to get the result.
37 Mismatches are errors, not warnings.
39 * Fixed incorrect processing of some invalid input.
41 * Fixed CPP guards: 9foo.h uses BISON_9FOO_H instead of 9FOO_H.
43 * Fixed some typos in the documentation.
45 * %token MY_EOF 0 is supported.
46 Before, MY_EOF was silently renumbered as 257.
48 * doc/refcard.tex is updated.
50 * %output, %file-prefix, %name-prefix.
54 New, aliasing `--output-file'.
56 Changes in version 1.30, 2001-10-26:
58 * `--defines' and `--graph' have now an optionnal argument which is the
59 output file name. `-d' and `-g' do not change, they do not take any
62 * `%source_extension' and `%header_extension' are removed, failed
67 Changes in version 1.29, 2001-09-07:
69 * The output file does not define const, as this caused problems when used
70 with common autoconfiguration schemes. If you still use ancient compilers
71 that lack const, compile with the equivalent of the C compiler option
72 `-Dconst='. autoconf's AC_C_CONST macro provides one way to do this.
74 * Added `-g' and `--graph'.
76 * The Bison manual is now distributed under the terms of the GNU FDL.
78 * The input and the output files has automatically a similar extension.
80 * Russian translation added.
82 * NLS support updated; should hopefully be less troublesome.
84 * Added the old Bison reference card.
86 * Added `--locations' and `%locations'.
88 * Added `-S' and `--skeleton'.
90 * `%raw', `-r', `--raw' is disabled.
92 * Special characters are escaped when output. This solves the problems
93 of the #line lines with path names including backslashes.
96 `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose',
97 `%debug', `%source_extension' and `%header_extension'.
100 Automatic location tracking.
102 Changes in version 1.28, 1999-07-06:
104 * Should compile better now with K&R compilers.
108 * Fixed a problem with escaping the double quote character.
110 * There is now a FAQ.
112 Changes in version 1.27:
114 * The make rule which prevented bison.simple from being created on
115 some systems has been fixed.
117 Changes in version 1.26:
119 * Bison now uses automake.
121 * New mailing lists: <bug-bison@gnu.org> and <help-bison@gnu.org>.
123 * Token numbers now start at 257 as previously documented, not 258.
125 * Bison honors the TMPDIR environment variable.
127 * A couple of buffer overruns have been fixed.
129 * Problems when closing files should now be reported.
131 * Generated parsers should now work even on operating systems which do
132 not provide alloca().
134 Changes in version 1.25, 1995-10-16:
136 * Errors in the input grammar are not fatal; Bison keeps reading
137 the grammar file, and reports all the errors found in it.
139 * Tokens can now be specified as multiple-character strings: for
140 example, you could use "<=" for a token which looks like <=, instead
141 of chosing a name like LESSEQ.
143 * The %token_table declaration says to write a table of tokens (names
144 and numbers) into the parser file. The yylex function can use this
145 table to recognize multiple-character string tokens, or for other
148 * The %no_lines declaration says not to generate any #line preprocessor
149 directives in the parser file.
151 * The %raw declaration says to use internal Bison token numbers, not
152 Yacc-compatible token numbers, when token names are defined as macros.
154 * The --no-parser option produces the parser tables without including
155 the parser engine; a project can now use its own parser engine.
156 The actions go into a separate file called NAME.act, in the form of
157 a switch statement body.
159 Changes in version 1.23:
161 The user can define YYPARSE_PARAM as the name of an argument to be
162 passed into yyparse. The argument should have type void *. It should
163 actually point to an object. Grammar actions can access the variable
164 by casting it to the proper pointer type.
166 Line numbers in output file corrected.
168 Changes in version 1.22:
172 Changes in version 1.20:
174 Output file does not redefine const for C++.