NEWS

   1 Bison News
   2 ----------
   3
   4 Changes in version 1.28a:
   5
   6 * Russian translation added.
   7
   8 * NLS support updated; should hopefully be less troublesome.
   9
  10 * Added the old Bison reference card.
  11
  12 * Added `--locations' and `%locations'.
  13
  14 * New directives.
  15   `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose', and
  16   `%debug'.
  17 \f
  18 Changes in version 1.28:
  19
  20 * Should compile better now with K&R compilers.
  21
  22 * Added NLS.
  23
  24 * Fixed a problem with escaping the double quote character.
  25
  26 * There is now a FAQ.
  27 \f
  28 Changes in version 1.27:
  29
  30 * The make rule which prevented bison.simple from being created on
  31   some systems has been fixed.
  32 \f
  33 Changes in version 1.26:
  34
  35 * Bison now uses automake.
  36
  37 * New mailing lists: <bug-bison@gnu.org> and <help-bison@gnu.org>.
  38
  39 * Token numbers now start at 257 as previously documented, not 258.
  40
  41 * Bison honors the TMPDIR environment variable.
  42
  43 * A couple of buffer overruns have been fixed.
  44
  45 * Problems when closing files should now be reported.
  46
  47 * Generated parsers should now work even on operating systems which do
  48   not provide alloca().
  49 \f
  50 Changes in version 1.25:
  51
  52 * Errors in the input grammar are not fatal; Bison keeps reading
  53 the grammar file, and reports all the errors found in it.
  54
  55 * Tokens can now be specified as multiple-character strings: for
  56 example, you could use "<=" for a token which looks like <=, instead
  57 of chosing a name like LESSEQ.
  58
  59 * The %token_table declaration says to write a table of tokens (names
  60 and numbers) into the parser file.  The yylex function can use this
  61 table to recognize multiple-character string tokens, or for other
  62 purposes.
  63
  64 * The %no_lines declaration says not to generate any #line preprocessor
  65 directives in the parser file.
  66
  67 * The %raw declaration says to use internal Bison token numbers, not
  68 Yacc-compatible token numbers, when token names are defined as macros.
  69
  70 * The --no-parser option produces the parser tables without including
  71 the parser engine; a project can now use its own parser engine.
  72 The actions go into a separate file called NAME.act, in the form of
  73 a switch statement body.
  74 \f
  75 Changes in version 1.23:
  76
  77 The user can define YYPARSE_PARAM as the name of an argument to be
  78 passed into yyparse.  The argument should have type void *.  It should
  79 actually point to an object.  Grammar actions can access the variable
  80 by casting it to the proper pointer type.
  81
  82 Line numbers in output file corrected.
  83 \f
  84 Changes in version 1.22:
  85
  86 --help option added.
  87 \f
  88 Changes in version 1.20:
  89
  90 Output file does not redefine const for C++.