Lines Matching full:declarations
99 * Grammar File:: Writing Bison declarations and rules.
154 * Decls: Rpcalc Decls. Prologue (declarations) for rpcalc.
170 * Decls: Ltcalc Decls. Bison and C declarations for ltcalc.
176 * Decl: Mfcalc Decl. Bison declarations for multi-function calculator.
188 * Declarations:: All kinds of Bison declarations are described here.
194 * Bison Declarations:: Syntax and usage of the Bison declarations section.
214 Bison Declarations
226 * Decl Summary:: Table of all Bison declarations.
469 With the proper declarations, Bison is also able to parse these more
547 language, the nonterminal symbol `sequence of definitions and declarations'
559 must be a `sequence of definitions and declarations'. If not, the parser
702 @code{%glr-parser} among the Bison declarations in your file
706 declarations) identically to @acronym{LALR}(1) parsers. However, when
785 (These declarations are contrived, but they are syntactically
788 These two declarations look identical until the @samp{..} token.
805 undefined identifiers. But if these declarations occur in a local
843 parses a vastly simplified form of Pascal type declarations.
895 adding these two declarations to the Bison input file (before the first
905 parser recognizes all valid declarations, according to the
987 certain declarations and statements. For example,
1012 declarations specify that Bison is to give precedence
1021 The @code{%dprec} declarations only come into play when more than one
1070 in the C declarations at the beginning of the file:
1080 With these declarations, the resulting parser parses the first example
1316 @var{Bison declarations}
1335 The Bison declarations declare the names of the terminal and nonterminal
1389 * Decls: Rpcalc Decls. Prologue (declarations) for rpcalc.
1399 @subsection Declarations for @code{rpcalc}
1401 Here are the C and Bison declarations for the reverse polish notation
1419 The declarations section (@pxref{Prologue, , The prologue}) contains two
1420 preprocessor directives and two forward declarations.
1433 The forward declarations for @code{yylex} and @code{yyerror} are
1439 The second section, Bison declarations, provides information to Bison
1440 about the token types (@pxref{Bison Declarations, ,The Bison
1441 Declarations Section}). Each terminal symbol that is not a
1649 ,Declarations for @code{rpcalc}}.)
1840 /* Bison declarations. */
1874 In the second section (Bison declarations), @code{%left} declares token
1875 types and says they are left-associative operators. The declarations
1883 declarations; the higher the line number of the declaration (lower on
1963 * Decls: Ltcalc Decls. Bison and C declarations for ltcalc.
1969 @subsection Declarations for @code{ltcalc}
1971 The C and Bison declarations for the location tracking calculator are
1972 the same as the declarations for the infix notation calculator.
1984 /* Bison declarations. */
1996 Note there are no declarations specific to locations. Defining a data
2202 * Decl: Mfcalc Decl. Bison declarations for multi-function calculator.
2208 @subsection Declarations for @code{mfcalc}
2210 Here are the C and Bison declarations for the multi-function calculator.
2253 declarations are augmented with information about their data type (placed
2309 grammar rules (except for the actions) or the Bison declarations, but it
2587 * Declarations:: All kinds of Bison declarations are described here.
2602 @var{Bison declarations}
2617 * Bison Declarations:: Syntax and usage of the Bison declarations section.
2624 @cindex declarations section
2626 @cindex declarations
2628 The @var{Prologue} section contains macro definitions and declarations
2632 @samp{#include} to get the declarations from a header file. If you
2633 don't need any C declarations, you may omit the @samp{%@{} and
2641 @var{Bison declarations}. This allows you to have C and Bison
2642 declarations that refer to each other. For example, the @code{%union}
2667 @node Bison Declarations
2668 @subsection The Bison Declarations Section
2669 @cindex Bison declarations (introduction)
2670 @cindex declarations, Bison (introduction)
2672 The @var{Bison declarations} section contains declarations that define
2674 In some simple grammars you may not need any declarations.
2675 @xref{Declarations, ,Bison Declarations}.
2785 Declarations}). If you don't do that, the lexical analyzer has to
3355 compound: '@{' declarations statements '@}'
3367 '@{' declarations statements '@}'
3389 '@{' declarations statements '@}'
3407 declarations statements '@}'
3430 '@{' declarations statements '@}'
3636 @node Declarations
3637 @section Bison Declarations
3638 @cindex declarations, Bison
3639 @cindex Bison declarations
3641 The @dfn{Bison declarations} section of a Bison grammar defines the symbols
3666 * Decl Summary:: Table of all Bison declarations.
3756 interchangeably in further declarations or the grammar rules. The
3762 @cindex precedence declarations
3768 once. These are called @dfn{precedence declarations}.
3786 And indeed any of these declarations serves the purposes of @code{%token}.
3806 When two tokens declared in different precedence declarations associate,
3835 in the @code{%token} and @code{%type} declarations to pick one of the types
3856 @code{%union} declarations; their contents are concatenated. However,
3887 terminal symbol. All kinds of token declarations allow
4111 Here is a summary of the declarations used to define a grammar:
4175 names defined in the grammar as well as a few other declarations.
4199 typically needs to be able to refer to the above-mentioned declarations
4246 declarations.
4719 declarations section (@pxref{Bison Declarations, ,The Bison Declarations
5216 operator precedence declarations. To see the reason for this, let's
5287 Bison declarations for operator precedence allow you to specify when to
5351 declarations @code{%left} and @code{%right}. Each such declaration
5368 In our example, we would want the following declarations:
5394 The first effect of the precedence declarations is to assign precedence
5426 The Bison precedence declarations, @code{%left}, @code{%right} and
5486 explicit precedence. This will probably add declarations to the
6055 is @emph{not} significant, such as in declarations that can shadow a
6725 calculator (@pxref{Mfcalc Decl, ,Declarations for @code{mfcalc}}):
6897 the grammar, as well as a few other declarations. @xref{Decl Summary}.
7428 Then come the declarations/inclusions needed to define the
8136 Bison declarations section or the epilogue.
