]> git.saurik.com Git - bison.git/blob - NEWS
Regen.
[bison.git] / NEWS
1 Bison News
2 ----------
3
4 Changes in version 1.33a:
5
6 * Revert the C++ namespace changes introduced in 1.31, as they caused too
7 many portability hassles.
8
9 * DJGPP support added.
10
11 * Fix portability problems within the test suite.
12 \f
13 Changes in version 1.33, 2002-02-07:
14
15 * Fix C++ issues
16 Groff could not be compiled for the definition of size_t was lacking
17 under some conditions.
18
19 * Catch invalid @n
20 As is done with $n.
21 \f
22 Changes in version 1.32, 2002-01-23:
23
24 * Fix Yacc output file names
25
26 * Portability fixes
27
28 * Italian, Dutch translations
29 \f
30 Changes in version 1.31, 2002-01-14:
31
32 * Many Bug Fixes
33
34 * GNU Gettext and %expect
35 GNU Gettext asserts 10 s/r conflicts, but there are 7. Now that
36 Bison dies on incorrect %expectations, we fear there will be
37 too many bug reports for Gettext, so _for the time being_, %expect
38 does not trigger an error when the input file is named `plural.y'.
39
40 * Use of alloca in parsers
41 If YYSTACK_USE_ALLOCA is defined to 0, then the parsers will use
42 malloc exclusively. Since 1.29, but was not NEWS'ed.
43
44 alloca is used only when compiled with GCC, to avoid portability
45 problems as on AIX.
46
47 * When the generated parser lacks debugging code, YYDEBUG is now 0
48 (as POSIX requires) instead of being undefined.
49
50 * User Actions
51 Bison has always permitted actions such as { $$ = $1 }: it adds the
52 ending semicolon. Now if in Yacc compatibility mode, the semicolon
53 is no longer output: one has to write { $$ = $1; }.
54
55 * Better C++ compliance
56 The output parsers try to respect C++ namespaces.
57 [This turned out to be a failed experiment, and it was reverted later.]
58
59 * Reduced Grammars
60 Fixed bugs when reporting useless nonterminals.
61
62 * 64 bit hosts
63 The parsers work properly on 64 bit hosts.
64
65 * Error messages
66 Some calls to strerror resulted in scrambled or missing error messages.
67
68 * %expect
69 When the number of shift/reduce conflicts is correct, don't issue
70 any warning.
71
72 * The verbose report includes the rule line numbers.
73
74 * Rule line numbers are fixed in traces.
75
76 * Swedish translation
77
78 * Parse errors
79 Verbose parse error messages from the parsers are better looking.
80 Before: parse error: unexpected `'/'', expecting `"number"' or `'-'' or `'(''
81 Now: parse error: unexpected '/', expecting "number" or '-' or '('
82
83 * Fixed parser memory leaks.
84 When the generated parser was using malloc to extend its stacks, the
85 previous allocations were not freed.
86
87 * Fixed verbose output file.
88 Some newlines were missing.
89 Some conflicts in state descriptions were missing.
90
91 * Fixed conflict report.
92 Option -v was needed to get the result.
93
94 * %expect
95 Was not used.
96 Mismatches are errors, not warnings.
97
98 * Fixed incorrect processing of some invalid input.
99
100 * Fixed CPP guards: 9foo.h uses BISON_9FOO_H instead of 9FOO_H.
101
102 * Fixed some typos in the documentation.
103
104 * %token MY_EOF 0 is supported.
105 Before, MY_EOF was silently renumbered as 257.
106
107 * doc/refcard.tex is updated.
108
109 * %output, %file-prefix, %name-prefix.
110 New.
111
112 * --output
113 New, aliasing `--output-file'.
114 \f
115 Changes in version 1.30, 2001-10-26:
116
117 * `--defines' and `--graph' have now an optionnal argument which is the
118 output file name. `-d' and `-g' do not change, they do not take any
119 argument.
120
121 * `%source_extension' and `%header_extension' are removed, failed
122 experiment.
123
124 * Portability fixes.
125 \f
126 Changes in version 1.29, 2001-09-07:
127
128 * The output file does not define const, as this caused problems when used
129 with common autoconfiguration schemes. If you still use ancient compilers
130 that lack const, compile with the equivalent of the C compiler option
131 `-Dconst='. autoconf's AC_C_CONST macro provides one way to do this.
132
133 * Added `-g' and `--graph'.
134
135 * The Bison manual is now distributed under the terms of the GNU FDL.
136
137 * The input and the output files has automatically a similar extension.
138
139 * Russian translation added.
140
141 * NLS support updated; should hopefully be less troublesome.
142
143 * Added the old Bison reference card.
144
145 * Added `--locations' and `%locations'.
146
147 * Added `-S' and `--skeleton'.
148
149 * `%raw', `-r', `--raw' is disabled.
150
151 * Special characters are escaped when output. This solves the problems
152 of the #line lines with path names including backslashes.
153
154 * New directives.
155 `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose',
156 `%debug', `%source_extension' and `%header_extension'.
157
158 * @$
159 Automatic location tracking.
160 \f
161 Changes in version 1.28, 1999-07-06:
162
163 * Should compile better now with K&R compilers.
164
165 * Added NLS.
166
167 * Fixed a problem with escaping the double quote character.
168
169 * There is now a FAQ.
170 \f
171 Changes in version 1.27:
172
173 * The make rule which prevented bison.simple from being created on
174 some systems has been fixed.
175 \f
176 Changes in version 1.26:
177
178 * Bison now uses automake.
179
180 * New mailing lists: <bug-bison@gnu.org> and <help-bison@gnu.org>.
181
182 * Token numbers now start at 257 as previously documented, not 258.
183
184 * Bison honors the TMPDIR environment variable.
185
186 * A couple of buffer overruns have been fixed.
187
188 * Problems when closing files should now be reported.
189
190 * Generated parsers should now work even on operating systems which do
191 not provide alloca().
192 \f
193 Changes in version 1.25, 1995-10-16:
194
195 * Errors in the input grammar are not fatal; Bison keeps reading
196 the grammar file, and reports all the errors found in it.
197
198 * Tokens can now be specified as multiple-character strings: for
199 example, you could use "<=" for a token which looks like <=, instead
200 of chosing a name like LESSEQ.
201
202 * The %token_table declaration says to write a table of tokens (names
203 and numbers) into the parser file. The yylex function can use this
204 table to recognize multiple-character string tokens, or for other
205 purposes.
206
207 * The %no_lines declaration says not to generate any #line preprocessor
208 directives in the parser file.
209
210 * The %raw declaration says to use internal Bison token numbers, not
211 Yacc-compatible token numbers, when token names are defined as macros.
212
213 * The --no-parser option produces the parser tables without including
214 the parser engine; a project can now use its own parser engine.
215 The actions go into a separate file called NAME.act, in the form of
216 a switch statement body.
217 \f
218 Changes in version 1.23:
219
220 The user can define YYPARSE_PARAM as the name of an argument to be
221 passed into yyparse. The argument should have type void *. It should
222 actually point to an object. Grammar actions can access the variable
223 by casting it to the proper pointer type.
224
225 Line numbers in output file corrected.
226 \f
227 Changes in version 1.22:
228
229 --help option added.
230 \f
231 Changes in version 1.20:
232
233 Output file does not redefine const for C++.
234
235 Local Variables:
236 mode: outline
237 End: