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