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