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