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