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