Lines Matching full:yyerror
250 * Error Reporting:: You must supply a function @code{yyerror}.
995 void yyerror (char const *);
1183 @findex YYERROR
1184 @cindex GLR parsers and @code{YYERROR}
1185 Another Bison feature requiring special consideration is @code{YYERROR}
1188 During deterministic GLR operation, the effect of @code{YYERROR} is
1299 error reporting function @code{yyerror} and the parser function
1391 printer @code{yyerror} here, along with any other global identifiers
1470 void yyerror (char const *);
1492 The forward declarations for @code{yylex} and @code{yyerror} are
1789 function @code{yyerror} to print an error message (usually but not
1791 @code{yyerror} (@pxref{Interface, ,Parser C-Language Interface}), so
1802 yyerror (char const *s)
1809 After @code{yyerror} returns, the Bison parser may recover from the error
1823 the grammar file. The definitions of @code{yylex}, @code{yyerror} and
1843 in the grammar file (@code{yylex}, @code{yyerror} and @code{main}) are
1911 void yyerror (char const *);
1955 The functions @code{yylex}, @code{yyerror} and @code{main} can be the
2000 error. All we have handled is error reporting with @code{yyerror}.
2002 @code{yyerror}. This means that an erroneous input line causes the
2022 and parsing will continue. (The @code{yyerror} function is still called
2026 difference between @code{yyerrok} and @code{yyerror}; neither one is a
2068 void yyerror (char const *);
2313 void yyerror (char const *);
2459 yyerror (char const *s)
2665 yyerror (char const *s)
3160 of @code{yylex} and @code{yyerror} often go here. Because C requires
3162 functions like @code{yylex} and @code{yyerror} in the Prologue, even
4480 Syntax error messages passed to @code{yyerror} from the parser will reference
4834 error via @code{YYERROR} are not discarded automatically. As a rule
5012 Reporting Function @code{yyerror}}). The convention for calling
5495 @code{yyerror} when the tracking of locations has been activated, as shown
5499 difference is in the signature of @code{yyerror} on Yacc parsers without
5503 @code{yyerror} are:
5506 void yyerror (char const *msg); // Yacc parsers.
5507 void yyerror (YYLTYPE *locp, char const *msg); // GLR parsers.
5514 void yyerror (YYLTYPE *llocp, int *nastiness, char const *msg);
5518 Reporting Function @code{yyerror}})
5799 The renamed symbols include @code{yyparse}, @code{yylex}, @code{yyerror},
5887 * Error Reporting:: You must supply a function @code{yyerror}.
5975 void yyerror (int *randomness, const char *msg);
5984 void yyerror (YYLTYPE *llocp, int *randomness, const char *msg);
6296 @section The Error Reporting Function @code{yyerror}
6298 @findex yyerror
6305 macro @code{YYERROR} (@pxref{Action Features, ,Special Features for Use
6309 reporting function named @code{yyerror}, which you must supply. It is
6325 if memory is exhausted, @code{yyparse} calls @code{yyerror} in the usual
6330 they are passed to @code{yyerror}. @xref{Internationalization}.
6337 yyerror (char const *s)
6346 After @code{yyerror} returns to @code{yyparse}, the latter will attempt
6351 Obviously, in location tracking pure parsers, @code{yyerror} should have
6357 When @code{%locations %define api.pure full} is used, @code{yyerror} has the
6361 void yyerror (YYLTYPE *locp, char const *msg);
6366 uses @code{yyerror}. Bison-generated code always ignores the returned
6367 value, so @code{yyerror} can return any type, including @code{void}.
6368 Also, @code{yyerror} can be a variadic function; that is why the
6371 Traditionally @code{yyerror} returns an @code{int} that is always
6374 @code{yyerror}.
6448 @deffn {Macro} YYERROR @code{;}
6451 does not call @code{yyerror}, and does not print any message. If you
6452 want to print an error message, call @code{yyerror} explicitly before
6453 the @samp{YYERROR;} statement. @xref{Error Recovery}.
7923 calls @code{yyerror} and then returns 2.
8211 void yyerror (char const *);
9622 @code{yyerror} and @code{main} functions. These default
9629 If you use the Yacc library's @code{yyerror} function, you should
9630 declare @code{yyerror} as follows:
9633 int yyerror (char const *);
9636 Bison ignores the @code{int} value returned by this @code{yyerror}.
10781 @deftypemethod {Lexer} {void} yyerror (Location @var{loc}, String @var{msg})
10872 @deftypefn {Statement} {return} YYERROR @code{;}
10884 @deftypefn {Function} {protected void} yyerror (String msg)
10885 @deftypefnx {Function} {protected void} yyerror (Position pos, String msg)
10886 @deftypefnx {Function} {protected void} yyerror (Location loc, String msg)
10887 Print an error message using the @code{yyerror} method of the scanner
10901 Java lacks a preprocessor, so the @code{YYERROR}, @code{YYACCEPT},
11672 when @code{yyerror} is called. @xref{Error Reporting}.
11721 @code{yylex}, @code{yyerror}, @code{yynerrs}, @code{yylval}, @code{yychar},
11820 function @code{yyerror} is not called. @xref{Parser Function, ,The
11869 @deffn {Macro} YYERROR
11872 does not call @code{yyerror}, and does not print any message. If you
11873 want to print an error message, call @code{yyerror} explicitly before
11874 the @samp{YYERROR;} statement. @xref{Error Recovery}.
11876 For Java parsers, this functionality is invoked using @code{return YYERROR;}
11880 @deffn {Function} yyerror
11883 Reporting Function @code{yyerror}}.
11889 when @code{yyerror} is called. It doesn't matter what definition you
11954 @xref{Error Reporting, ,The Error Reporting Function @code{yyerror}}.
12308 @c LocalWords: yyerror pxref LR yylval cindex dfn LALR samp gpl BNF xref yypush
