| | 1 | Bison News |
| | 2 | ---------- |
| | 3 | |
| | 4 | Change in version 1.25: |
| | 5 | |
| | 6 | * Errors in the input grammar are not fatal; Bison keeps reading |
| | 7 | the grammar file, and reports all the errors found in it. |
| | 8 | |
| | 9 | * Tokens can now be specified as multiple-character strings: for |
| | 10 | example, you could use "<=" for a token which looks like <=, instead |
| | 11 | of chosing a name like LESSEQ. |
| | 12 | |
| | 13 | * The %token_table declaration says to write a table of tokens (names |
| | 14 | and numbers) into the parser file. The yylex function can use this |
| | 15 | table to recognize multiple-character string tokens, or for other |
| | 16 | purposes. |
| | 17 | |
| | 18 | * The %no_lines declaration says not to generate any #line preprocessor |
| | 19 | directives in the parser file. |
| | 20 | |
| | 21 | * The %raw declaration says to use internal Bison token numbers, not |
| | 22 | Yacc-compatible token numbers, when token names are defined as macros. |
| | 23 | |
| | 24 | * The --no-parser option produces the parser tables without including |
| | 25 | the parser engine; a project can now use its own parser engine. |
| | 26 | The actions go into a separate file called NAME.act, in the form of |
| | 27 | a switch statement body. |
| | 28 | \f |
| | 29 | Changes in version 1.23: |
| | 30 | |
| | 31 | The user can define YYPARSE_PARAM as the name of an argument to be |
| | 32 | passed into yyparse. The argument should have type void *. It should |
| | 33 | actually point to an object. Grammar actions can access the variable |
| | 34 | by casting it to the proper pointer type. |
| | 35 | |
| | 36 | Line numbers in output file corrected. |
| | 37 | \f |
| | 38 | Changes in version 1.22: |
| | 39 | |
| | 40 | --help option added. |
| | 41 | \f |
| | 42 | Changes in version 1.20: |
| | 43 | |
| | 44 | Output file does not redefine const for C++. |
projects / bison.git / blame_incremental