NEWS

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