47 |
Therefore 0 cannot be used, since it would be both the rule number |
Therefore 0 cannot be used, since it would be both the rule number |
48 |
0, and the token EOF). |
0, and the token EOF). |
49 |
|
|
50 |
Actions and guards are accessed via the rule number. |
Actions are accessed via the rule number. |
51 |
|
|
52 |
The rules themselves are described by several arrays: amongst which |
The rules themselves are described by several arrays: amongst which |
53 |
RITEM, and RULES. |
RITEM, and RULES. |
150 |
|
|
151 |
const char *action; |
const char *action; |
152 |
int action_line; |
int action_line; |
|
|
|
|
const char *guard; |
|
|
int guard_line; |
|
153 |
} rule_t; |
} rule_t; |
154 |
|
|
155 |
extern struct rule_s *rules; |
extern struct rule_s *rules; |
163 |
extern token_number_t *token_translations; |
extern token_number_t *token_translations; |
164 |
extern int max_user_token_number; |
extern int max_user_token_number; |
165 |
|
|
|
/* SEMANTIC_PARSER is nonzero if the input file says to use the hairy |
|
|
parser that provides for semantic error recovery. If it is zero, |
|
|
the yacc-compatible simplified parser is used. */ |
|
|
|
|
|
extern int semantic_parser; |
|
166 |
|
|
167 |
/* PURE_PARSER is nonzero if should generate a parser that is all pure |
/* PURE_PARSER is nonzero if should generate a parser that is all pure |
168 |
and reentrant. */ |
and reentrant. */ |