NEWS

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