Lines Matching full:convention
220 * Calling Convention:: How `yyparse' calls `yylex'.
226 * Pure Calling:: How the calling convention differs in a pure parser
1291 input as an identifier, like an identifier in C. By convention, it
1296 identifiers. By convention, these identifiers should be upper case to
2003 extension is a convention used for Bison grammar files.
2220 The formatting shown here is the recommended convention, but Bison
3535 By convention, it should be all lower case.
3549 identifier in C. By convention, it should be all upper case. Each
3561 By convention, a character token type is used only to represent a
3564 Nothing enforces this convention, but if you depart from it, your
3570 end-of-input (*note Calling Convention for `yylex': Calling
3571 Convention.). Also, unlike standard C, trigraphs have no special
3585 token from the `yytname' table (*note Calling Convention::).
3589 By convention, a literal string token is used only to represent a
3592 Bison does not enforce this convention, but if you depart from it,
3617 make sense in terminal symbols.) *Note Calling Convention for `yylex':
3618 Calling Convention.
4595 the token type code number (*note Calling Convention::). Syntax error
5019 become local variables in `yyparse', and a different calling convention
5024 Function `yyerror': Error Reporting.). The convention for calling
5935 * Calling Convention:: How `yyparse' calls `yylex'.
5941 * Pure Calling:: How the calling convention differs in a pure parser
5945 File: bison.info, Node: Calling Convention, Next: Token Values, Up: Lexical
5947 4.6.1 Calling Convention for `yylex'
6020 File: bison.info, Node: Token Values, Next: Token Locations, Prev: Calling Convention, Up: Lexical
6521 established convention is that these ambiguities are resolved by
12763 Node: Calling Convention242626
