NEWS

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