NEWS

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