Lines Matching full:prologue
118 * Rpcalc Declarations:: Prologue (declarations) for rpcalc.
158 * Prologue:: Syntax and usage of the prologue.
159 * Prologue Alternatives:: Syntax and usage of alternatives to the prologue.
1931 PROLOGUE
1944 The prologue may define types and variables used in the actions.
1959 definitions of functions declared in the prologue go here. In a simple
2007 * Rpcalc Declarations:: Prologue (declarations) for rpcalc.
2037 The declarations section (*note The prologue: Prologue.) contains two
2053 parser calls them so they must be declared in the prologue.
3147 PROLOGUE
3164 * Prologue:: Syntax and usage of the prologue.
3165 * Prologue Alternatives:: Syntax and usage of alternatives to the prologue.
3171 File: bison.info, Node: Prologue, Next: Prologue Alternatives, Up: Grammar Outline
3173 3.1.1 The prologue
3176 The PROLOGUE section contains macro definitions and declarations of
3184 The PROLOGUE section is terminated by the first occurrence of `%}'
3187 You may have more than one PROLOGUE section, intermixed with the
3192 two PROLOGUE blocks, one before and one after the `%union' declaration.
3212 When in doubt, it is usually safer to put prologue code before all
3219 File: bison.info, Node: Prologue Alternatives, Next: Bison Declarations, Prev: Prologue, Up: Grammar Outline
3221 3.1.2 Prologue Alternatives
3224 The functionality of PROLOGUE sections can often be subtle and
3251 Notice that there are two PROLOGUE sections here, but there's a subtle
3253 override Bison's default definition for `YYLTYPE', in which PROLOGUE
3257 which PROLOGUE section should you prototype an internal function,
3262 This distinction in functionality between the two PROLOGUE sections
3267 PROLOGUE section is not available. This behavior is not intuitive.
3306 functionality as the two kinds of PROLOGUE sections, but it's always
3372 requires' to be the most important of the four PROLOGUE alternatives.
3457 organization is not possible using PROLOGUE sections.
3460 the four PROLOGUE alternatives over the original Yacc PROLOGUE.
3469 File: bison.info, Node: Bison Declarations, Next: Grammar Rules, Prev: Prologue Alternatives, Up: Grammar Outline
3499 file, just as the PROLOGUE is copied to the beginning. This is the
3505 `yyerror' in the Prologue, even if you define them in the Epilogue.
3825 in the prologue of the grammar file (*note Outline of a Bison Grammar:
5568 prologue, `%{CODE%}'. This section summarizes the functionality of
5571 C/C++ and why it is advantageous to do so, *note Prologue
7812 The declaration of `hexflag' shown in the prologue of the grammar
7814 Prologue: Prologue.). You must also write the code in `yylex' to obey
8451 YYDEBUG 1' in the prologue of the grammar file (*note The
8452 Prologue: Prologue.).
8530 its prologue:
10188 * The prologue declarations have a different meaning than in C/C++
10565 /* Prologue. */
10749 parser implementation file. Such code forms the prologue of the
11013 An obsolete macro that you define with `#define' in the prologue
11935 * %code <4>: Prologue Alternatives.
11948 * %code provides <2>: Prologue Alternatives.
11954 * %code requires: Prologue Alternatives.
11956 * %code top <1>: Prologue Alternatives.
12225 * declarations: Prologue. (line 6)
12226 * declarations section: Prologue. (line 6)
12460 * Prologue <1>: %code Summary. (line 6)
12461 * Prologue: Prologue. (line 6)
12462 * Prologue Alternatives: Prologue Alternatives.
12717 Node: Prologue133228
12718 Node: Prologue Alternatives135032
