30 |
user specified that one of her tokens is numbered 256, then error |
user specified that one of her tokens is numbered 256, then error |
31 |
will be mapped onto another number. |
will be mapped onto another number. |
32 |
|
|
33 |
|
* Verbose error messages |
34 |
|
They no longer report `..., expecting error or...' for state where |
35 |
|
error recovery is possible. |
36 |
|
|
37 |
|
* End token |
38 |
|
Defaults to `$end' instead of `$'. |
39 |
|
|
40 |
* Error recovery now conforms to documentation and to POSIX |
* Error recovery now conforms to documentation and to POSIX |
41 |
When a Bison-generated parser encounters a syntax error, it now pops |
When a Bison-generated parser encounters a syntax error, it now pops |
42 |
the stack until it finds a state that allows shifting the error |
the stack until it finds a state that allows shifting the error |
91 |
* Token end-of-file |
* Token end-of-file |
92 |
The token end of file may be specified by the user, in which case, |
The token end of file may be specified by the user, in which case, |
93 |
the user symbol is used in the reports, the graphs, and the verbose |
the user symbol is used in the reports, the graphs, and the verbose |
94 |
error messages instead of `$', which remains being the defaults. |
error messages instead of `$end', which remains being the defaults. |
95 |
For instance |
For instance |
96 |
%token YYEOF 0 |
%token YYEOF 0 |
97 |
or |
or |