Lines Matching full:calling
240 * Calling Convention:: How @code{yyparse} calls @code{yylex}.
246 * Pure Calling:: How the calling convention differs
726 involved, or by performing both actions, and then calling a designated
1625 tokens by calling the lexical analyzer. @xref{Lexical, ,The Lexical
1915 Recall that by default @code{yyparse} returns after calling
2768 end-of-input (@pxref{Calling Convention, ,Calling Convention
2787 @code{yytname} table (@pxref{Calling Convention}).
2820 @xref{Calling Convention, ,Calling Convention for @code{yylex}}.
3758 obtain the token type code number (@pxref{Calling Convention}).
4094 calling convention is used for the lexical analyzer function
4095 @code{yylex}. @xref{Pure Calling, ,Calling Conventions for Pure
4098 Reporting Function @code{yyerror}}). The convention for calling
4471 * Calling Convention:: How @code{yyparse} calls @code{yylex}.
4477 * Pure Calling:: How the calling convention differs
4481 @node Calling Convention
4482 @subsection Calling Convention for @code{yylex}
4629 @node Pure Calling
4630 @subsection Calling Conventions for Pure Parsers
4711 The Bison parser expects to report the error by calling an error
4772 Finally, @acronym{GLR} and Yacc parsers share the same @code{yyerror} calling
4773 convention for absolutely pure parsers, i.e., when the calling
4774 convention of @code{yylex} @emph{and} the calling convention of
7215 The parser invokes the scanner by calling @code{yylex}. Contrary to C
8242 @code{yylex} should accept. @xref{Pure Calling,, Calling Conventions
8419 @xref{Pure Calling,, Calling Conventions for Pure Parsers}.
8468 is supported only for Yacc like parsers. @xref{Pure Calling,, Calling
