Lines Matching full:convention
257 * Calling Convention:: How @code{yyparse} calls @code{yylex}.
263 * Pure Calling:: How the calling convention differs in a pure parser
624 as an identifier, like an identifier in C@. By convention, it should be
629 convention, these identifiers should be upper case to distinguish them from
1445 @samp{.y} extension is a convention used for Bison grammar files.
1666 The formatting shown here is the recommended convention, but Bison does
3194 By convention, it should be all lower case.
3209 identifier in C@. By convention, it should be all upper case. Each
3225 By convention, a character token type is used only to represent a
3228 token. Nothing enforces this convention, but if you depart from it,
3234 end-of-input (@pxref{Calling Convention, ,Calling Convention
3253 @code{yytname} table (@pxref{Calling Convention}).
3257 By convention, a literal string token is used only to represent a token
3260 does not enforce this convention, but if you depart from it, people who
3286 Convention, ,Calling Convention for @code{yylex}}.
4479 obtain the token type code number (@pxref{Calling Convention}).
5007 calling convention is used for the lexical analyzer function
5012 Reporting Function @code{yyerror}}). The convention for calling
6078 * Calling Convention:: How @code{yyparse} calls @code{yylex}.
6084 * Pure Calling:: How the calling convention differs in a pure parser
6088 @node Calling Convention
6089 @subsection Calling Convention for @code{yylex}
6805 convention is that these ambiguities are resolved by attaching the
