Lines Matching full:yyerror
213 * Error Reporting:: You must supply a function `yyerror'.
1611 void yyerror (char const *);
1763 Another Bison feature requiring special consideration is `YYERROR'
1766 effect of `YYERROR' is the same as its effect in a deterministic parser.
1870 `yyerror' and the parser function `yyparse' itself. This also includes
1948 `yyerror' here, along with any other global identifiers used by the
2030 void yyerror (char const *);
2050 The forward declarations for `yylex' and `yyerror' are needed
2328 function `yyerror' to print an error message (usually but not always
2329 `"syntax error"'). It is up to the programmer to supply `yyerror'
2337 yyerror (char const *s)
2342 After `yyerror' returns, the Bison parser may recover from the error
2358 grammar file. The definitions of `yylex', `yyerror' and `main' go at
2374 additional functions in the grammar file (`yylex', `yyerror' and
2432 void yyerror (char const *);
2465 The functions `yylex', `yyerror' and `main' can be the same as before.
2507 error. All we have handled is error reporting with `yyerror'. Recall
2508 that by default `yyparse' returns after calling `yyerror'. This means
2525 parsing will continue. (The `yyerror' function is still called upon to
2529 difference between `yyerrok' and `yyerror'; neither one is a misprint.
2572 void yyerror (char const *);
2787 void yyerror (char const *);
2911 yyerror (char const *s)
3077 yyerror (char const *s)
3503 `yyerror' often go here. Because C requires functions to be declared
3505 `yyerror' in the Prologue, even if you define them in the Epilogue.
4596 messages passed to `yyerror' from the parser will reference the literal
4874 error via `YYERROR' are not discarded automatically. As a rule of
5024 Function `yyerror': Error Reporting.). The convention for calling
5429 Calling::), and also that of `yyerror' when the tracking of
5433 difference is in the signature of `yyerror' on Yacc parsers
5437 prototypes for `yyerror' are:
5439 void yyerror (char const *msg); // Yacc parsers.
5440 void yyerror (YYLTYPE *locp, char const *msg); // GLR parsers.
5446 void yyerror (YYLTYPE *llocp, int *nastiness, char const *msg);
5448 (*note The Error Reporting Function `yyerror': Error
5681 The renamed symbols include `yyparse', `yylex', `yyerror',
5763 * Error Reporting:: You must supply a function `yyerror'.
5832 void yyerror (int *randomness, const char *msg);
5838 void yyerror (YYLTYPE *llocp, int *randomness, const char *msg);
6124 4.7 The Error Reporting Function `yyerror'
6130 `YYERROR' (*note Special Features for Use in Actions: Action Features.).
6133 reporting function named `yyerror', which you must supply. It is
6149 limit. But if memory is exhausted, `yyparse' calls `yyerror' in the
6154 passed to `yyerror'. *Note Internationalization::.
6159 yyerror (char const *s)
6164 After `yyerror' returns to `yyparse', the latter will attempt error
6169 Obviously, in location tracking pure parsers, `yyerror' should have
6175 When `%locations %define api.pure full' is used, `yyerror' has the
6178 void yyerror (YYLTYPE *locp, char const *msg);
6181 uses `yyerror'. Bison-generated code always ignores the returned
6182 value, so `yyerror' can return any type, including `void'. Also,
6183 `yyerror' can be a variadic function; that is why the message is always
6186 Traditionally `yyerror' returns an `int' that is always ignored, but
6188 it more accurately describes the return type for `yyerror'.
6250 -- Macro: YYERROR `;'
6253 however, it does not call `yyerror', and does not print any
6254 message. If you want to print an error message, call `yyerror'
6255 explicitly before the `YYERROR;' statement. *Note Error
7521 `yyparse' calls `yyerror' and then returns 2.
7790 void yyerror (char const *);
9072 The Yacc library contains default implementations of the `yyerror' and
9079 If you use the Yacc library's `yyerror' function, you should declare
9080 `yyerror' as follows:
9082 int yyerror (char const *);
9084 Bison ignores the `int' value returned by this `yyerror'. If you
10065 -- Method on Lexer: void yyerror (Location LOC, String MSG)
10143 -- Statement: return YYERROR `;'
10152 -- Function: protected void yyerror (String msg)
10153 -- Function: protected void yyerror (Position pos, String msg)
10154 -- Function: protected void yyerror (Location loc, String msg)
10155 Print an error message using the `yyerror' method of the scanner
10168 * Java lacks a preprocessor, so the `YYERROR', `YYACCEPT', `YYABORT'
10839 strings when `yyerror' is called. *Note Error Reporting::.
10882 `yylex', `yyerror', `yynerrs', `yylval', `yychar', `yydebug', and
10956 function `yyerror' is not called. *Note The Parser Function
10997 -- Macro: YYERROR
11000 however, it does not call `yyerror', and does not print any
11001 message. If you want to print an error message, call `yyerror'
11002 explicitly before the `YYERROR;' statement. *Note Error
11006 YYERROR;' instead.
11008 -- Function: yyerror
11010 The Error Reporting Function `yyerror': Error Reporting.
11014 to request verbose, specific error message strings when `yyerror'
11068 *Note The Error Reporting Function `yyerror': Error Reporting.
12308 * GLR parsers and YYERROR: GLR Semantic Actions.
12591 * yyerror: Java Action Features.
12593 * YYERROR <1>: Java Action Features.
12595 * YYERROR: Action Features. (line 56)
12596 * yyerror <1>: Error Reporting. (line 6)
12597 * yyerror: Table of Symbols. (line 309)
12598 * YYERROR <1>: Table of Symbols. (line 298)
12599 * YYERROR: GLR Semantic Actions.
12601 * yyerror: Java Action Features.
12603 * yyerror on Lexer: Java Scanner Interface.
