doc: save width.

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index aa82db97e915c853a652779458db67abe4656bff..a5cdf52a435568fc4ebd57da5d3690fa6b64a4d4 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -536,7 +536,6 @@ lexicography, not grammar.)
 
 Here is a simple C function subdivided into tokens:
 
 
 Here is a simple C function subdivided into tokens:
 

-@ifinfo

 @example
 int             /* @r{keyword `int'} */
 square (int x)  /* @r{identifier, open-paren, keyword `int',}
 @example
 int             /* @r{keyword `int'} */
 square (int x)  /* @r{identifier, open-paren, keyword `int',}


@@ -546,16 +545,6 @@ square (int x)  /* @r{identifier, open-paren, keyword `int',}
                    @r{identifier, semicolon} */
 @}               /* @r{close-brace} */
 @end example
                    @r{identifier, semicolon} */
 @}               /* @r{close-brace} */
 @end example

-@end ifinfo
-@ifnotinfo
-@example
-int             /* @r{keyword `int'} */
-square (int x)  /* @r{identifier, open-paren, keyword `int', identifier, close-paren} */
-@{               /* @r{open-brace} */
-  return x * x; /* @r{keyword `return', identifier, asterisk, identifier, semicolon} */
-@}               /* @r{close-brace} */
-@end example
-@end ifnotinfo

 
 The syntactic groupings of C include the expression, the statement, the
 declaration, and the function definition.  These are represented in the
 
 The syntactic groupings of C include the expression, the statement, the
 declaration, and the function definition.  These are represented in the


@@ -637,8 +626,7 @@ the statement; the naked semicolon, and the colon, are Bison punctuation
 used in every rule.
 
 @example
 used in every rule.
 
 @example

-stmt:   RETURN expr ';'
-        ;
+stmt: RETURN expr ';' ;

 @end example
 
 @noindent
 @end example
 
 @noindent


@@ -710,8 +698,7 @@ For example, here is a rule that says an expression can be the sum of
 two subexpressions:
 
 @example
 two subexpressions:
 
 @example

-expr: expr '+' expr   @{ $$ = $1 + $3; @}
-        ;
+expr: expr '+' expr   @{ $$ = $1 + $3; @} ;

 @end example
 
 @noindent
 @end example
 
 @noindent


@@ -890,30 +877,32 @@ parses a vastly simplified form of Pascal type declarations.
 %%
 
 @group
 %%
 
 @group

-type_decl : TYPE ID '=' type ';'
-     ;
+type_decl: TYPE ID '=' type ';' ;

 @end group
 
 @group
 @end group
 
 @group

-type : '(' id_list ')'
-     | expr DOTDOT expr
-     ;
+type:
+  '(' id_list ')'
+| expr DOTDOT expr
+;

 @end group
 
 @group
 @end group
 
 @group

-id_list : ID
-     | id_list ',' ID
-     ;
+id_list:
+  ID
+| id_list ',' ID
+;

 @end group
 
 @group
 @end group
 
 @group

-expr : '(' expr ')'
-     | expr '+' expr
-     | expr '-' expr
-     | expr '*' expr
-     | expr '/' expr
-     | ID
-     ;
+expr:
+  '(' expr ')'
+| expr '+' expr
+| expr '-' expr
+| expr '*' expr
+| expr '/' expr
+| ID
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -993,30 +982,35 @@ Let's consider an example, vastly simplified from a C++ grammar.
 
 %%
 
 
 %%
 

-prog :
-     | prog stmt   @{ printf ("\n"); @}
-     ;
+prog:
+  /* Nothing.  */
+| prog stmt   @{ printf ("\n"); @}
+;

 
 

-stmt : expr ';'  %dprec 1
-     | decl      %dprec 2
-     ;
+stmt:
+  expr ';'  %dprec 1
+| decl      %dprec 2
+;

 
 

-expr : ID               @{ printf ("%s ", $$); @}
-     | TYPENAME '(' expr ')'
-                        @{ printf ("%s <cast> ", $1); @}
-     | expr '+' expr    @{ printf ("+ "); @}
-     | expr '=' expr    @{ printf ("= "); @}
-     ;
+expr:
+  ID               @{ printf ("%s ", $$); @}
+| TYPENAME '(' expr ')'
+                   @{ printf ("%s <cast> ", $1); @}
+| expr '+' expr    @{ printf ("+ "); @}
+| expr '=' expr    @{ printf ("= "); @}
+;

 
 

-decl : TYPENAME declarator ';'
-                        @{ printf ("%s <declare> ", $1); @}
-     | TYPENAME declarator '=' expr ';'
-                        @{ printf ("%s <init-declare> ", $1); @}
-     ;
+decl:
+  TYPENAME declarator ';'
+                   @{ printf ("%s <declare> ", $1); @}
+| TYPENAME declarator '=' expr ';'
+                   @{ printf ("%s <init-declare> ", $1); @}
+;

 
 

-declarator : ID         @{ printf ("\"%s\" ", $1); @}
-     | '(' declarator ')'
-     ;
+declarator:
+  ID               @{ printf ("\"%s\" ", $1); @}
+| '(' declarator ')'
+;

 @end example
 
 @noindent
 @end example
 
 @noindent


@@ -1085,9 +1079,10 @@ other.  To do so, you could change the declaration of @code{stmt} as
 follows:
 
 @example
 follows:
 
 @example

-stmt : expr ';'  %merge <stmtMerge>
-     | decl      %merge <stmtMerge>
-     ;
+stmt:
+  expr ';'  %merge <stmtMerge>
+| decl      %merge <stmtMerge>
+;

 @end example
 
 @noindent
 @end example
 
 @noindent


@@ -1494,25 +1489,28 @@ Here are the grammar rules for the reverse polish notation calculator.
 
 @example
 @group
 
 @example
 @group

-input:    /* empty */
-        | input line
+input:
+  /* empty */
+| input line

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-line:     '\n'
-        | exp '\n'      @{ printf ("\t%.10g\n", $1); @}
+line:
+  '\n'
+| exp '\n'      @{ printf ("%.10g\n", $1); @}

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-exp:      NUM           @{ $$ = $1;           @}
-        | exp exp '+'   @{ $$ = $1 + $2;      @}
-        | exp exp '-'   @{ $$ = $1 - $2;      @}
-        | exp exp '*'   @{ $$ = $1 * $2;      @}
-        | exp exp '/'   @{ $$ = $1 / $2;      @}
-        | exp exp '^'   @{ $$ = pow ($1, $2); @}  /* Exponentiation */
-        | exp 'n'       @{ $$ = -$1;          @}  /* Unary minus    */
+exp:
+  NUM           @{ $$ = $1;           @}
+| exp exp '+'   @{ $$ = $1 + $2;      @}
+| exp exp '-'   @{ $$ = $1 - $2;      @}
+| exp exp '*'   @{ $$ = $1 * $2;      @}
+| exp exp '/'   @{ $$ = $1 / $2;      @}
+| exp exp '^'   @{ $$ = pow ($1, $2); @}  /* Exponentiation */
+| exp 'n'       @{ $$ = -$1;          @}  /* Unary minus    */

 ;
 @end group
 %%
 ;
 @end group
 %%


@@ -1548,8 +1546,9 @@ rule are referred to as @code{$1}, @code{$2}, and so on.
 Consider the definition of @code{input}:
 
 @example
 Consider the definition of @code{input}:
 
 @example

-input:    /* empty */
-        | input line
+input:
+  /* empty */
+| input line

 ;
 @end example
 
 ;
 @end example
 


@@ -1582,8 +1581,9 @@ input tokens; we will arrange for the latter to happen at end-of-input.
 Now consider the definition of @code{line}:
 
 @example
 Now consider the definition of @code{line}:
 
 @example

-line:     '\n'
-        | exp '\n'  @{ printf ("\t%.10g\n", $1); @}
+line:
+  '\n'
+| exp '\n'  @{ printf ("%.10g\n", $1); @}

 ;
 @end example
 
 ;
 @end example
 


@@ -1610,21 +1610,22 @@ The second handles an addition-expression, which looks like two expressions
 followed by a plus-sign.  The third handles subtraction, and so on.
 
 @example
 followed by a plus-sign.  The third handles subtraction, and so on.
 
 @example

-exp:      NUM
-        | exp exp '+'     @{ $$ = $1 + $2;    @}
-        | exp exp '-'     @{ $$ = $1 - $2;    @}
-        @dots{}
-        ;
+exp:
+  NUM
+| exp exp '+'     @{ $$ = $1 + $2;    @}
+| exp exp '-'     @{ $$ = $1 - $2;    @}
+@dots{}
+;

 @end example
 
 We have used @samp{|} to join all the rules for @code{exp}, but we could
 equally well have written them separately:
 
 @example
 @end example
 
 We have used @samp{|} to join all the rules for @code{exp}, but we could
 equally well have written them separately:
 
 @example

-exp:      NUM ;
-exp:      exp exp '+'     @{ $$ = $1 + $2;    @} ;
-exp:      exp exp '-'     @{ $$ = $1 - $2;    @} ;
-        @dots{}
+exp: NUM ;
+exp: exp exp '+'     @{ $$ = $1 + $2; @};
+exp: exp exp '-'     @{ $$ = $1 - $2; @};
+@dots{}

 @end example
 
 Most of the rules have actions that compute the value of the expression in
 @end example
 
 Most of the rules have actions that compute the value of the expression in


@@ -1645,16 +1646,17 @@ not require it.  You can add or change white space as much as you wish.
 For example, this:
 
 @example
 For example, this:
 
 @example

-exp   : NUM | exp exp '+' @{$$ = $1 + $2; @} | @dots{} ;
+exp: NUM | exp exp '+' @{$$ = $1 + $2; @} | @dots{} ;

 @end example
 
 @noindent
 means the same thing as this:
 
 @example
 @end example
 
 @noindent
 means the same thing as this:
 
 @example

-exp:      NUM
-        | exp exp '+'    @{ $$ = $1 + $2; @}
-        | @dots{}
+exp:
+  NUM
+| exp exp '+'    @{ $$ = $1 + $2; @}
+| @dots{}

 ;
 @end example
 
 ;
 @end example
 


@@ -1899,26 +1901,29 @@ parentheses nested to arbitrary depth.  Here is the Bison code for
 
 %% /* The grammar follows.  */
 @group
 
 %% /* The grammar follows.  */
 @group

-input:    /* empty */
-        | input line
+input:
+  /* empty */
+| input line

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-line:     '\n'
-        | exp '\n'  @{ printf ("\t%.10g\n", $1); @}
+line:
+  '\n'
+| exp '\n'  @{ printf ("\t%.10g\n", $1); @}

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-exp:      NUM                @{ $$ = $1;           @}
-        | exp '+' exp        @{ $$ = $1 + $3;      @}
-        | exp '-' exp        @{ $$ = $1 - $3;      @}
-        | exp '*' exp        @{ $$ = $1 * $3;      @}
-        | exp '/' exp        @{ $$ = $1 / $3;      @}
-        | '-' exp  %prec NEG @{ $$ = -$2;          @}
-        | exp '^' exp        @{ $$ = pow ($1, $3); @}
-        | '(' exp ')'        @{ $$ = $2;           @}
+exp:
+  NUM                @{ $$ = $1;           @}
+| exp '+' exp        @{ $$ = $1 + $3;      @}
+| exp '-' exp        @{ $$ = $1 - $3;      @}
+| exp '*' exp        @{ $$ = $1 * $3;      @}
+| exp '/' exp        @{ $$ = $1 / $3;      @}
+| '-' exp  %prec NEG @{ $$ = -$2;          @}
+| exp '^' exp        @{ $$ = pow ($1, $3); @}
+| '(' exp ')'        @{ $$ = $2;           @}

 ;
 @end group
 %%
 ;
 @end group
 %%


@@ -1981,9 +1986,10 @@ been added to one of the alternatives for @code{line}:
 
 @example
 @group
 
 @example
 @group

-line:     '\n'
-        | exp '\n'   @{ printf ("\t%.10g\n", $1); @}
-        | error '\n' @{ yyerrok;                  @}
+line:
+  '\n'
+| exp '\n'   @{ printf ("\t%.10g\n", $1); @}
+| error '\n' @{ yyerrok;                  @}

 ;
 @end group
 @end example
 ;
 @end group
 @end example


@@ -2074,41 +2080,44 @@ wrong expressions or subexpressions.
 
 @example
 @group
 
 @example
 @group

-input   : /* empty */
-        | input line
+input:
+  /* empty */
+| input line

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-line    : '\n'
-        | exp '\n' @{ printf ("%d\n", $1); @}
+line:
+  '\n'
+| exp '\n' @{ printf ("%d\n", $1); @}

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-exp     : NUM           @{ $$ = $1; @}
-        | exp '+' exp   @{ $$ = $1 + $3; @}
-        | exp '-' exp   @{ $$ = $1 - $3; @}
-        | exp '*' exp   @{ $$ = $1 * $3; @}
+exp:
+  NUM           @{ $$ = $1; @}
+| exp '+' exp   @{ $$ = $1 + $3; @}
+| exp '-' exp   @{ $$ = $1 - $3; @}
+| exp '*' exp   @{ $$ = $1 * $3; @}

 @end group
 @group
 @end group
 @group

-        | exp '/' exp
-            @{
-              if ($3)
-                $$ = $1 / $3;
-              else
-                @{
-                  $$ = 1;
-                  fprintf (stderr, "%d.%d-%d.%d: division by zero",
-                           @@3.first_line, @@3.first_column,
-                           @@3.last_line, @@3.last_column);
-                @}
-            @}
+| exp '/' exp
+    @{
+      if ($3)
+        $$ = $1 / $3;
+      else
+        @{
+          $$ = 1;
+          fprintf (stderr, "%d.%d-%d.%d: division by zero",
+                   @@3.first_line, @@3.first_column,
+                   @@3.last_line, @@3.last_column);
+        @}
+    @}

 @end group
 @group
 @end group
 @group

-        | '-' exp %prec NEG     @{ $$ = -$2; @}
-        | exp '^' exp           @{ $$ = pow ($1, $3); @}
-        | '(' exp ')'           @{ $$ = $2; @}
+| '-' exp %prec NEG     @{ $$ = -$2; @}
+| exp '^' exp           @{ $$ = pow ($1, $3); @}
+| '(' exp ')'           @{ $$ = $2; @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -2272,7 +2281,8 @@ Note that multiple assignment and nested function calls are permitted.
 
 Here are the C and Bison declarations for the multi-function calculator.
 
 
 Here are the C and Bison declarations for the multi-function calculator.
 

-@smallexample
+@comment file: mfcalc.y
+@example

 @group
 %@{
   #include <math.h>  /* For math functions, cos(), sin(), etc.  */
 @group
 %@{
   #include <math.h>  /* For math functions, cos(), sin(), etc.  */


@@ -2299,7 +2309,7 @@ Here are the C and Bison declarations for the multi-function calculator.
 %right '^'    /* exponentiation */
 @end group
 %% /* The grammar follows.  */
 %right '^'    /* exponentiation */
 @end group
 %% /* The grammar follows.  */

-@end smallexample
+@end example

 
 The above grammar introduces only two new features of the Bison language.
 These features allow semantic values to have various data types
 
 The above grammar introduces only two new features of the Bison language.
 These features allow semantic values to have various data types


@@ -2330,38 +2340,41 @@ Here are the grammar rules for the multi-function calculator.
 Most of them are copied directly from @code{calc}; three rules,
 those which mention @code{VAR} or @code{FNCT}, are new.
 
 Most of them are copied directly from @code{calc}; three rules,
 those which mention @code{VAR} or @code{FNCT}, are new.
 

-@smallexample
+@comment file: mfcalc.y
+@example

 @group
 @group

-input:   /* empty */
-        | input line
+input:
+  /* empty */
+| input line

 ;
 @end group
 
 @group
 line:
 ;
 @end group
 
 @group
 line:

-          '\n'
-        | exp '\n'   @{ printf ("\t%.10g\n", $1); @}
-        | error '\n' @{ yyerrok;                  @}
+  '\n'
+| exp '\n'   @{ printf ("%.10g\n", $1); @}
+| error '\n' @{ yyerrok;                @}

 ;
 @end group
 
 @group
 ;
 @end group
 
 @group

-exp:      NUM                @{ $$ = $1;                         @}
-        | VAR                @{ $$ = $1->value.var;              @}
-        | VAR '=' exp        @{ $$ = $3; $1->value.var = $3;     @}
-        | FNCT '(' exp ')'   @{ $$ = (*($1->value.fnctptr))($3); @}
-        | exp '+' exp        @{ $$ = $1 + $3;                    @}
-        | exp '-' exp        @{ $$ = $1 - $3;                    @}
-        | exp '*' exp        @{ $$ = $1 * $3;                    @}
-        | exp '/' exp        @{ $$ = $1 / $3;                    @}
-        | '-' exp  %prec NEG @{ $$ = -$2;                        @}
-        | exp '^' exp        @{ $$ = pow ($1, $3);               @}
-        | '(' exp ')'        @{ $$ = $2;                         @}
+exp:
+  NUM                @{ $$ = $1;                         @}
+| VAR                @{ $$ = $1->value.var;              @}
+| VAR '=' exp        @{ $$ = $3; $1->value.var = $3;     @}
+| FNCT '(' exp ')'   @{ $$ = (*($1->value.fnctptr))($3); @}
+| exp '+' exp        @{ $$ = $1 + $3;                    @}
+| exp '-' exp        @{ $$ = $1 - $3;                    @}
+| exp '*' exp        @{ $$ = $1 * $3;                    @}
+| exp '/' exp        @{ $$ = $1 / $3;                    @}
+| '-' exp  %prec NEG @{ $$ = -$2;                        @}
+| exp '^' exp        @{ $$ = pow ($1, $3);               @}
+| '(' exp ')'        @{ $$ = $2;                         @}

 ;
 @end group
 /* End of grammar.  */
 %%
 ;
 @end group
 /* End of grammar.  */
 %%

-@end smallexample
+@end example

 
 @node Mfcalc Symbol Table
 @subsection The @code{mfcalc} Symbol Table
 
 @node Mfcalc Symbol Table
 @subsection The @code{mfcalc} Symbol Table


@@ -2376,7 +2389,8 @@ The symbol table itself consists of a linked list of records.  Its
 definition, which is kept in the header @file{calc.h}, is as follows.  It
 provides for either functions or variables to be placed in the table.
 
 definition, which is kept in the header @file{calc.h}, is as follows.  It
 provides for either functions or variables to be placed in the table.
 

-@smallexample
+@comment file: calc.h
+@example

 @group
 /* Function type.  */
 typedef double (*func_t) (double);
 @group
 /* Function type.  */
 typedef double (*func_t) (double);


@@ -2406,13 +2420,13 @@ extern symrec *sym_table;
 symrec *putsym (char const *, int);
 symrec *getsym (char const *);
 @end group
 symrec *putsym (char const *, int);
 symrec *getsym (char const *);
 @end group

-@end smallexample
+@end example

 
 The new version of @code{main} includes a call to @code{init_table}, a
 function that initializes the symbol table.  Here it is, and
 @code{init_table} as well:
 
 
 The new version of @code{main} includes a call to @code{init_table}, a
 function that initializes the symbol table.  Here it is, and
 @code{init_table} as well:
 

-@smallexample
+@example

 #include <stdio.h>
 
 @group
 #include <stdio.h>
 
 @group


@@ -2472,7 +2486,7 @@ main (void)
   return yyparse ();
 @}
 @end group
   return yyparse ();
 @}
 @end group

-@end smallexample
+@end example

 
 By simply editing the initialization list and adding the necessary include
 files, you can add additional functions to the calculator.
 
 By simply editing the initialization list and adding the necessary include
 files, you can add additional functions to the calculator.


@@ -2484,7 +2498,8 @@ linked to the front of the list, and a pointer to the object is returned.
 The function @code{getsym} is passed the name of the symbol to look up.  If
 found, a pointer to that symbol is returned; otherwise zero is returned.
 
 The function @code{getsym} is passed the name of the symbol to look up.  If
 found, a pointer to that symbol is returned; otherwise zero is returned.
 

-@smallexample
+@comment file: mfcalc.y
+@example

 #include <stdlib.h> /* malloc. */
 #include <string.h> /* strlen. */
 
 #include <stdlib.h> /* malloc. */
 #include <string.h> /* strlen. */
 


@@ -2515,7 +2530,7 @@ getsym (char const *sym_name)
   return 0;
 @}
 @end group
   return 0;
 @}
 @end group

-@end smallexample
+@end example

 
 The function @code{yylex} must now recognize variables, numeric values, and
 the single-character arithmetic operators.  Strings of alphanumeric
 
 The function @code{yylex} must now recognize variables, numeric values, and
 the single-character arithmetic operators.  Strings of alphanumeric


@@ -2532,7 +2547,8 @@ returned to @code{yyparse}.
 No change is needed in the handling of numeric values and arithmetic
 operators in @code{yylex}.
 
 No change is needed in the handling of numeric values and arithmetic
 operators in @code{yylex}.
 

-@smallexample
+@comment file: mfcalc.y
+@example

 @group
 #include <ctype.h>
 @end group
 @group
 #include <ctype.h>
 @end group


@@ -2573,7 +2589,6 @@ yylex (void)
       int i;
 @end group
 
       int i;
 @end group
 

-@group

       if (!symbuf)
         symbuf = (char *) malloc (length + 1);
 
       if (!symbuf)
         symbuf = (char *) malloc (length + 1);
 


@@ -2612,7 +2627,7 @@ yylex (void)
   return c;
 @}
 @end group
   return c;
 @}
 @end group

-@end smallexample
+@end example

 
 This program is both powerful and flexible.  You may easily add new
 functions, and it is a simple job to modify this code to install
 
 This program is both powerful and flexible.  You may easily add new
 functions, and it is a simple job to modify this code to install


@@ -2715,7 +2730,7 @@ prototype functions that take arguments of type @code{YYSTYPE}.  This
 can be done with two @var{Prologue} blocks, one before and one after the
 @code{%union} declaration.
 
 can be done with two @var{Prologue} blocks, one before and one after the
 @code{%union} declaration.
 

-@smallexample
+@example

 %@{
   #define _GNU_SOURCE
   #include <stdio.h>
 %@{
   #define _GNU_SOURCE
   #include <stdio.h>


@@ -2733,7 +2748,7 @@ can be done with two @var{Prologue} blocks, one before and one after the
 %@}
 
 @dots{}
 %@}
 
 @dots{}

-@end smallexample
+@end example

 
 When in doubt, it is usually safer to put prologue code before all
 Bison declarations, rather than after.  For example, any definitions
 
 When in doubt, it is usually safer to put prologue code before all
 Bison declarations, rather than after.  For example, any definitions


@@ -2761,7 +2776,7 @@ location, or it can be one of @code{requires}, @code{provides},
 
 Look again at the example of the previous section:
 
 
 Look again at the example of the previous section:
 

-@smallexample
+@example

 %@{
   #define _GNU_SOURCE
   #include <stdio.h>
 %@{
   #define _GNU_SOURCE
   #include <stdio.h>


@@ -2779,7 +2794,7 @@ Look again at the example of the previous section:
 %@}
 
 @dots{}
 %@}
 
 @dots{}

-@end smallexample
+@end example

 
 @noindent
 Notice that there are two @var{Prologue} sections here, but there's a
 
 @noindent
 Notice that there are two @var{Prologue} sections here, but there's a


@@ -2808,7 +2823,7 @@ To avoid this subtle @code{%union} dependency, rewrite the example using a
 Let's go ahead and add the new @code{YYLTYPE} definition and the
 @code{trace_token} prototype at the same time:
 
 Let's go ahead and add the new @code{YYLTYPE} definition and the
 @code{trace_token} prototype at the same time:
 

-@smallexample
+@example

 %code top @{
   #define _GNU_SOURCE
   #include <stdio.h>
 %code top @{
   #define _GNU_SOURCE
   #include <stdio.h>


@@ -2840,7 +2855,7 @@ Let's go ahead and add the new @code{YYLTYPE} definition and the
 @}
 
 @dots{}
 @}
 
 @dots{}

-@end smallexample
+@end example

 
 @noindent
 In this way, @code{%code top} and the unqualified @code{%code} achieve the same
 
 @noindent
 In this way, @code{%code top} and the unqualified @code{%code} achieve the same


@@ -2864,7 +2879,7 @@ lines are dependency code required by the @code{YYSTYPE} and @code{YYLTYPE}
 definitions.
 Thus, they belong in one or more @code{%code requires}:
 
 definitions.
 Thus, they belong in one or more @code{%code requires}:
 

-@smallexample
+@example

 @group
 %code top @{
   #define _GNU_SOURCE
 @group
 %code top @{
   #define _GNU_SOURCE


@@ -2907,7 +2922,7 @@ Thus, they belong in one or more @code{%code requires}:
 @end group
 
 @dots{}
 @end group
 
 @dots{}

-@end smallexample
+@end example

 
 @noindent
 Now Bison will insert @code{#include "ptypes.h"} and the new
 
 @noindent
 Now Bison will insert @code{#include "ptypes.h"} and the new


@@ -2941,7 +2956,7 @@ this function is not a dependency required by @code{YYSTYPE} or
 sufficient.  Instead, move its prototype from the unqualified
 @code{%code} to a @code{%code provides}:
 
 sufficient.  Instead, move its prototype from the unqualified
 @code{%code} to a @code{%code provides}:
 

-@smallexample
+@example

 @group
 %code top @{
   #define _GNU_SOURCE
 @group
 %code top @{
   #define _GNU_SOURCE


@@ -2989,7 +3004,7 @@ sufficient.  Instead, move its prototype from the unqualified
 @end group
 
 @dots{}
 @end group
 
 @dots{}

-@end smallexample
+@end example

 
 @noindent
 Bison will insert the @code{trace_token} prototype into both the
 
 @noindent
 Bison will insert the @code{trace_token} prototype into both the


@@ -3015,7 +3030,7 @@ organize your grammar file.
 For example, you may organize semantic-type-related directives by semantic
 type:
 
 For example, you may organize semantic-type-related directives by semantic
 type:
 

-@smallexample
+@example

 @group
 %code requires @{ #include "type1.h" @}
 %union @{ type1 field1; @}
 @group
 %code requires @{ #include "type1.h" @}
 %union @{ type1 field1; @}


@@ -3029,7 +3044,7 @@ type:
 %destructor @{ type2_free ($$); @} <field2>
 %printer @{ type2_print ($$); @} <field2>
 @end group
 %destructor @{ type2_free ($$); @} <field2>
 %printer @{ type2_print ($$); @} <field2>
 @end group

-@end smallexample
+@end example

 
 @noindent
 You could even place each of the above directive groups in the rules section of
 
 @noindent
 You could even place each of the above directive groups in the rules section of


@@ -3257,8 +3272,7 @@ A Bison grammar rule has the following general form:
 
 @example
 @group
 
 @example
 @group

-@var{result}: @var{components}@dots{}
-        ;
+@var{result}: @var{components}@dots{};

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3271,8 +3285,7 @@ For example,
 
 @example
 @group
 
 @example
 @group

-exp:      exp '+' exp
-        ;
+exp: exp '+' exp;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3317,10 +3330,11 @@ be joined with the vertical-bar character @samp{|} as follows:
 
 @example
 @group
 
 @example
 @group

-@var{result}:    @var{rule1-components}@dots{}
-        | @var{rule2-components}@dots{}
-        @dots{}
-        ;
+@var{result}:
+  @var{rule1-components}@dots{}
+| @var{rule2-components}@dots{}
+@dots{}
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3333,15 +3347,17 @@ comma-separated sequence of zero or more @code{exp} groupings:
 
 @example
 @group
 
 @example
 @group

-expseq:   /* empty */
-        | expseq1
-        ;
+expseq:
+  /* empty */
+| expseq1
+;

 @end group
 
 @group
 @end group
 
 @group

-expseq1:  exp
-        | expseq1 ',' exp
-        ;
+expseq1:
+  exp
+| expseq1 ',' exp
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3361,9 +3377,10 @@ comma-separated sequence of one or more expressions:
 
 @example
 @group
 
 @example
 @group

-expseq1:  exp
-        | expseq1 ',' exp
-        ;
+expseq1:
+  exp
+| expseq1 ',' exp
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3376,9 +3393,10 @@ the same construct is defined using @dfn{right recursion}:
 
 @example
 @group
 
 @example
 @group

-expseq1:  exp
-        | exp ',' expseq1
-        ;
+expseq1:
+  exp
+| exp ',' expseq1
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3402,15 +3420,17 @@ For example:
 
 @example
 @group
 
 @example
 @group

-expr:     primary
-        | primary '+' primary
-        ;
+expr:
+  primary
+| primary '+' primary
+;

 @end group
 
 @group
 @end group
 
 @group

-primary:  constant
-        | '(' expr ')'
-        ;
+primary:
+  constant
+| '(' expr ')'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3532,9 +3552,9 @@ Here is a typical example:
 
 @example
 @group
 
 @example
 @group

-exp:    @dots{}
-        | exp '+' exp
-            @{ $$ = $1 + $3; @}
+exp:
+@dots{}
+| exp '+' exp     @{ $$ = $1 + $3; @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3542,9 +3562,9 @@ Or, in terms of named references:
 
 @example
 @group
 
 @example
 @group

-exp[result]:    @dots{}
-        | exp[left] '+' exp[right]
-            @{ $result = $left + $right; @}
+exp[result]:
+@dots{}
+| exp[left] '+' exp[right]  @{ $result = $left + $right; @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3591,15 +3611,16 @@ is a case in which you can use this reliably:
 
 @example
 @group
 
 @example
 @group

-foo:      expr bar '+' expr  @{ @dots{} @}
-        | expr bar '-' expr  @{ @dots{} @}
-        ;
+foo:
+  expr bar '+' expr  @{ @dots{} @}
+| expr bar '-' expr  @{ @dots{} @}
+;

 @end group
 
 @group
 @end group
 
 @group

-bar:      /* empty */
-        @{ previous_expr = $0; @}
-        ;
+bar:
+  /* empty */    @{ previous_expr = $0; @}
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3629,9 +3650,9 @@ in the rule.  In this example,
 
 @example
 @group
 
 @example
 @group

-exp:    @dots{}
-        | exp '+' exp
-            @{ $$ = $1 + $3; @}
+exp:
+  @dots{}
+| exp '+' exp    @{ $$ = $1 + $3; @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3698,11 +3719,11 @@ remove it afterward.  Here is how it is done:
 
 @example
 @group
 
 @example
 @group

-stmt:   LET '(' var ')'
-                @{ $<context>$ = push_context ();
-                  declare_variable ($3); @}
-        stmt    @{ $$ = $6;
-                  pop_context ($<context>5); @}
+stmt:
+  LET '(' var ')'
+    @{ $<context>$ = push_context (); declare_variable ($3); @}
+  stmt
+    @{ $$ = $6; pop_context ($<context>5); @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3744,15 +3765,19 @@ declare a destructor for that symbol:
 
 %%
 
 
 %%
 

-stmt:  let stmt
-               @{ $$ = $2;
-                 pop_context ($1); @}
-       ;
+stmt:
+  let stmt
+    @{
+      $$ = $2;
+      pop_context ($1);
+    @};

 
 

-let:   LET '(' var ')'
-               @{ $$ = push_context ();
-                 declare_variable ($3); @}
-       ;
+let:
+  LET '(' var ')'
+    @{
+      $$ = push_context ();
+      declare_variable ($3);
+    @};

 
 @end group
 @end example
 
 @end group
 @end example


@@ -3771,9 +3796,10 @@ declaration or not:
 
 @example
 @group
 
 @example
 @group

-compound: '@{' declarations statements '@}'
-        | '@{' statements '@}'
-        ;
+compound:
+  '@{' declarations statements '@}'
+| '@{' statements '@}'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3782,12 +3808,13 @@ But when we add a mid-rule action as follows, the rules become nonfunctional:
 
 @example
 @group
 
 @example
 @group

-compound: @{ prepare_for_local_variables (); @}
-          '@{' declarations statements '@}'
+compound:
+  @{ prepare_for_local_variables (); @}
+     '@{' declarations statements '@}'

 @end group
 @group
 @end group
 @group

-        | '@{' statements '@}'
-        ;
+|    '@{' statements '@}'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3804,11 +3831,12 @@ actions into the two rules, like this:
 
 @example
 @group
 
 @example
 @group

-compound: @{ prepare_for_local_variables (); @}
-          '@{' declarations statements '@}'
-        | @{ prepare_for_local_variables (); @}
-          '@{' statements '@}'
-        ;
+compound:
+  @{ prepare_for_local_variables (); @}
+    '@{' declarations statements '@}'
+| @{ prepare_for_local_variables (); @}
+    '@{' statements '@}'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3822,10 +3850,11 @@ does work is to put the action after the open-brace, like this:
 
 @example
 @group
 
 @example
 @group

-compound: '@{' @{ prepare_for_local_variables (); @}
-          declarations statements '@}'
-        | '@{' statements '@}'
-        ;
+compound:
+  '@{' @{ prepare_for_local_variables (); @}
+    declarations statements '@}'
+| '@{' statements '@}'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3838,18 +3867,16 @@ serves as a subroutine:
 
 @example
 @group
 
 @example
 @group

-subroutine: /* empty */
-          @{ prepare_for_local_variables (); @}
-        ;
-
+subroutine:
+  /* empty */  @{ prepare_for_local_variables (); @}
+;

 @end group
 
 @group
 @end group
 
 @group

-compound: subroutine
-          '@{' declarations statements '@}'
-        | subroutine
-          '@{' statements '@}'
-        ;
+compound:
+  subroutine '@{' declarations statements '@}'
+| subroutine '@{' statements '@}'
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3934,24 +3961,25 @@ Here is a basic example using the default data type for locations:
 
 @example
 @group
 
 @example
 @group

-exp:    @dots{}
-        | exp '/' exp
-            @{
-              @@$.first_column = @@1.first_column;
-              @@$.first_line = @@1.first_line;
-              @@$.last_column = @@3.last_column;
-              @@$.last_line = @@3.last_line;
-              if ($3)
-                $$ = $1 / $3;
-              else
-                @{
-                  $$ = 1;
-                  fprintf (stderr,
-                           "Division by zero, l%d,c%d-l%d,c%d",
-                           @@3.first_line, @@3.first_column,
-                           @@3.last_line, @@3.last_column);
-                @}
-            @}
+exp:
+  @dots{}
+| exp '/' exp
+    @{
+      @@$.first_column = @@1.first_column;
+      @@$.first_line = @@1.first_line;
+      @@$.last_column = @@3.last_column;
+      @@$.last_line = @@3.last_line;
+      if ($3)
+        $$ = $1 / $3;
+      else
+        @{
+          $$ = 1;
+          fprintf (stderr,
+                   "Division by zero, l%d,c%d-l%d,c%d",
+                   @@3.first_line, @@3.first_column,
+                   @@3.last_line, @@3.last_column);
+        @}
+    @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -3965,20 +3993,21 @@ example above simply rewrites this way:
 
 @example
 @group
 
 @example
 @group

-exp:    @dots{}
-        | exp '/' exp
-            @{
-              if ($3)
-                $$ = $1 / $3;
-              else
-                @{
-                  $$ = 1;
-                  fprintf (stderr,
-                           "Division by zero, l%d,c%d-l%d,c%d",
-                           @@3.first_line, @@3.first_column,
-                           @@3.last_line, @@3.last_column);
-                @}
-            @}
+exp:
+  @dots{}
+| exp '/' exp
+    @{
+      if ($3)
+        $$ = $1 / $3;
+      else
+        @{
+          $$ = 1;
+          fprintf (stderr,
+                   "Division by zero, l%d,c%d-l%d,c%d",
+                   @@3.first_line, @@3.first_column,
+                   @@3.last_line, @@3.last_column);
+        @}
+    @}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -4019,27 +4048,27 @@ parameter is the number of discarded symbols.
 
 By default, @code{YYLLOC_DEFAULT} is defined this way:
 
 
 By default, @code{YYLLOC_DEFAULT} is defined this way:
 

-@smallexample
+@example

 @group
 @group

-# define YYLLOC_DEFAULT(Current, Rhs, N)                                \
-    do                                                                  \
-      if (N)                                                            \
-        @{                                                               \
-          (Current).first_line   = YYRHSLOC(Rhs, 1).first_line;         \
-          (Current).first_column = YYRHSLOC(Rhs, 1).first_column;       \
-          (Current).last_line    = YYRHSLOC(Rhs, N).last_line;          \
-          (Current).last_column  = YYRHSLOC(Rhs, N).last_column;        \
-        @}                                                               \
-      else                                                              \
-        @{                                                               \
-          (Current).first_line   = (Current).last_line   =              \
-            YYRHSLOC(Rhs, 0).last_line;                                 \
-          (Current).first_column = (Current).last_column =              \
-            YYRHSLOC(Rhs, 0).last_column;                               \
-        @}                                                               \
-    while (0)
+# define YYLLOC_DEFAULT(Cur, Rhs, N)                      \
+do                                                        \
+  if (N)                                                  \
+    @{                                                     \
+      (Cur).first_line   = YYRHSLOC(Rhs, 1).first_line;   \
+      (Cur).first_column = YYRHSLOC(Rhs, 1).first_column; \
+      (Cur).last_line    = YYRHSLOC(Rhs, N).last_line;    \
+      (Cur).last_column  = YYRHSLOC(Rhs, N).last_column;  \
+    @}                                                     \
+  else                                                    \
+    @{                                                     \
+      (Cur).first_line   = (Cur).last_line   =            \
+        YYRHSLOC(Rhs, 0).last_line;                       \
+      (Cur).first_column = (Cur).last_column =            \
+        YYRHSLOC(Rhs, 0).last_column;                     \
+    @}                                                     \
+while (0)

 @end group
 @end group

-@end smallexample
+@end example

 
 @noindent
 where @code{YYRHSLOC (rhs, k)} is the location of the @var{k}th symbol
 
 @noindent
 where @code{YYRHSLOC (rhs, k)} is the location of the @var{k}th symbol


@@ -4551,7 +4580,7 @@ symbol that has no declared semantic type tag.
 @noindent
 For example:
 
 @noindent
 For example:
 

-@smallexample
+@example

 %union @{ char *string; @}
 %token <string> STRING1
 %token <string> STRING2
 %union @{ char *string; @}
 %token <string> STRING1
 %token <string> STRING2


@@ -4566,7 +4595,7 @@ For example:
 %destructor @{ free ($$); @} <*>
 %destructor @{ free ($$); printf ("%d", @@$.first_line); @} STRING1 string1
 %destructor @{ printf ("Discarding tagless symbol.\n"); @} <>
 %destructor @{ free ($$); @} <*>
 %destructor @{ free ($$); printf ("%d", @@$.first_line); @} STRING1 string1
 %destructor @{ printf ("Discarding tagless symbol.\n"); @} <>

-@end smallexample
+@end example

 
 @noindent
 guarantees that, when the parser discards any user-defined symbol that has a
 
 @noindent
 guarantees that, when the parser discards any user-defined symbol that has a


@@ -4591,9 +4620,9 @@ reference it in your grammar.
 However, it may invoke one of them for the end token (token 0) if you
 redefine it from @code{$end} to, for example, @code{END}:
 
 However, it may invoke one of them for the end token (token 0) if you
 redefine it from @code{$end} to, for example, @code{END}:
 

-@smallexample
+@example

 %token END 0
 %token END 0

-@end smallexample
+@end example

 
 @cindex actions in mid-rule
 @cindex mid-rule actions
 
 @cindex actions in mid-rule
 @cindex mid-rule actions


@@ -5180,6 +5209,7 @@ Unaccepted @var{variable}s produce an error.
 Some of the accepted @var{variable}s are:
 
 @itemize @bullet
 Some of the accepted @var{variable}s are:
 
 @itemize @bullet

+@c ================================================== api.pure

 @item api.pure
 @findex %define api.pure
 
 @item api.pure
 @findex %define api.pure
 


@@ -5414,12 +5444,12 @@ should usually be more appropriate than @code{%code top}.  However,
 occasionally it is necessary to insert code much nearer the top of the
 parser implementation file.  For example:
 
 occasionally it is necessary to insert code much nearer the top of the
 parser implementation file.  For example:
 

-@smallexample
+@example

 %code top @{
   #define _GNU_SOURCE
   #include <stdio.h>
 @}
 %code top @{
   #define _GNU_SOURCE
   #include <stdio.h>
 @}

-@end smallexample
+@end example

 
 @item Location(s): Near the top of the parser implementation file.
 @end itemize
 
 @item Location(s): Near the top of the parser implementation file.
 @end itemize


@@ -5742,7 +5772,7 @@ assuming that the characters of the token are stored in
 @code{token_buffer}, and assuming that the token does not contain any
 characters like @samp{"} that require escaping.
 
 @code{token_buffer}, and assuming that the token does not contain any
 characters like @samp{"} that require escaping.
 

-@smallexample
+@example

 for (i = 0; i < YYNTOKENS; i++)
   @{
     if (yytname[i] != 0
 for (i = 0; i < YYNTOKENS; i++)
   @{
     if (yytname[i] != 0


@@ -5753,7 +5783,7 @@ for (i = 0; i < YYNTOKENS; i++)
         && yytname[i][strlen (token_buffer) + 2] == 0)
       break;
   @}
         && yytname[i][strlen (token_buffer) + 2] == 0)
       break;
   @}

-@end smallexample
+@end example

 
 The @code{yytname} table is generated only if you use the
 @code{%token-table} declaration.  @xref{Decl Summary}.
 
 The @code{yytname} table is generated only if you use the
 @code{%token-table} declaration.  @xref{Decl Summary}.


@@ -6350,16 +6380,18 @@ factorial operators (@samp{!}), and allow parentheses for grouping.
 
 @example
 @group
 
 @example
 @group

-expr:     term '+' expr
-        | term
-        ;
+expr:
+  term '+' expr
+| term
+;

 @end group
 
 @group
 @end group
 
 @group

-term:     '(' expr ')'
-        | term '!'
-        | NUMBER
-        ;
+term:
+  '(' expr ')'
+| term '!'
+| NUMBER
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6397,9 +6429,9 @@ statements, with a pair of rules like this:
 @example
 @group
 if_stmt:
 @example
 @group
 if_stmt:

-          IF expr THEN stmt
-        | IF expr THEN stmt ELSE stmt
-        ;
+  IF expr THEN stmt
+| IF expr THEN stmt ELSE stmt
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6466,20 +6498,22 @@ the conflict:
 %%
 @end group
 @group
 %%
 @end group
 @group

-stmt:     expr
-        | if_stmt
-        ;
+stmt:
+  expr
+| if_stmt
+;

 @end group
 
 @group
 if_stmt:
 @end group
 
 @group
 if_stmt:

-          IF expr THEN stmt
-        | IF expr THEN stmt ELSE stmt
-        ;
+  IF expr THEN stmt
+| IF expr THEN stmt ELSE stmt
+;

 @end group
 
 @end group
 

-expr:     variable
-        ;
+expr:
+  variable
+;

 @end example
 
 @node Precedence
 @end example
 
 @node Precedence


@@ -6507,12 +6541,13 @@ input @w{@samp{1 - 2 * 3}} can be parsed in two different ways):
 
 @example
 @group
 
 @example
 @group

-expr:     expr '-' expr
-        | expr '*' expr
-        | expr '<' expr
-        | '(' expr ')'
-        @dots{}
-        ;
+expr:
+  expr '-' expr
+| expr '*' expr
+| expr '<' expr
+| '(' expr ')'
+@dots{}
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6666,10 +6701,11 @@ Now the precedence of @code{UMINUS} can be used in specific rules:
 
 @example
 @group
 
 @example
 @group

-exp:    @dots{}
-        | exp '-' exp
-        @dots{}
-        | '-' exp %prec UMINUS
+exp:
+  @dots{}
+| exp '-' exp
+  @dots{}
+| '-' exp %prec UMINUS

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6735,20 +6771,18 @@ of zero or more @code{word} groupings.
 
 @example
 @group
 
 @example
 @group

-sequence: /* empty */
-                @{ printf ("empty sequence\n"); @}
-        | maybeword
-        | sequence word
-                @{ printf ("added word %s\n", $2); @}
-        ;
+sequence:
+  /* empty */    @{ printf ("empty sequence\n"); @}
+| maybeword
+| sequence word  @{ printf ("added word %s\n", $2); @}
+;

 @end group
 
 @group
 @end group
 
 @group

-maybeword: /* empty */
-                @{ printf ("empty maybeword\n"); @}
-        | word
-                @{ printf ("single word %s\n", $1); @}
-        ;
+maybeword:
+  /* empty */   @{ printf ("empty maybeword\n"); @}
+| word          @{ printf ("single word %s\n", $1); @}
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6776,28 +6810,30 @@ reduce/reduce conflict must be studied and usually eliminated.  Here is the
 proper way to define @code{sequence}:
 
 @example
 proper way to define @code{sequence}:
 
 @example

-sequence: /* empty */
-                @{ printf ("empty sequence\n"); @}
-        | sequence word
-                @{ printf ("added word %s\n", $2); @}
-        ;
+sequence:
+  /* empty */    @{ printf ("empty sequence\n"); @}
+| sequence word  @{ printf ("added word %s\n", $2); @}
+;

 @end example
 
 Here is another common error that yields a reduce/reduce conflict:
 
 @example
 @end example
 
 Here is another common error that yields a reduce/reduce conflict:
 
 @example

-sequence: /* empty */
-        | sequence words
-        | sequence redirects
-        ;
+sequence:
+  /* empty */
+| sequence words
+| sequence redirects
+;

 
 

-words:    /* empty */
-        | words word
-        ;
+words:
+  /* empty */
+| words word
+;

 
 

-redirects:/* empty */
-        | redirects redirect
-        ;
+redirects:
+  /* empty */
+| redirects redirect
+;

 @end example
 
 @noindent
 @end example
 
 @noindent


@@ -6816,10 +6852,11 @@ Here are two ways to correct these rules.  First, to make it a single level
 of sequence:
 
 @example
 of sequence:
 
 @example

-sequence: /* empty */
-        | sequence word
-        | sequence redirect
-        ;
+sequence:
+  /* empty */
+| sequence word
+| sequence redirect
+;

 @end example
 
 Second, to prevent either a @code{words} or a @code{redirects}
 @end example
 
 Second, to prevent either a @code{words} or a @code{redirects}


@@ -6827,22 +6864,25 @@ from being empty:
 
 @example
 @group
 
 @example
 @group

-sequence: /* empty */
-        | sequence words
-        | sequence redirects
-        ;
+sequence:
+  /* empty */
+| sequence words
+| sequence redirects
+;

 @end group
 
 @group
 @end group
 
 @group

-words:    word
-        | words word
-        ;
+words:
+  word
+| words word
+;

 @end group
 
 @group
 @end group
 
 @group

-redirects:redirect
-        | redirects redirect
-        ;
+redirects:
+  redirect
+| redirects redirect
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6858,30 +6898,27 @@ Here is an example:
 %token ID
 
 %%
 %token ID
 
 %%

-def:    param_spec return_spec ','
-        ;
+def: param_spec return_spec ',';

 param_spec:
 param_spec:

-             type
-        |    name_list ':' type
-        ;
+  type
+| name_list ':' type
+;

 @end group
 @group
 return_spec:
 @end group
 @group
 return_spec:

-             type
-        |    name ':' type
-        ;
+  type
+| name ':' type
+;

 @end group
 @group
 @end group
 @group

-type:        ID
-        ;
+type: ID;

 @end group
 @group
 @end group
 @group

-name:        ID
-        ;
+name: ID;

 name_list:
 name_list:

-             name
-        |    name ',' name_list
-        ;
+  name
+| name ',' name_list
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6930,11 +6967,10 @@ distinct.  In the above example, adding one rule to
 %%
 @dots{}
 return_spec:
 %%
 @dots{}
 return_spec:

-             type
-        |    name ':' type
-        /* This rule is never used.  */
-        |    ID BOGUS
-        ;
+  type
+| name ':' type
+| ID BOGUS       /* This rule is never used.  */
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -6954,13 +6990,13 @@ rather than the one for @code{name}.
 
 @example
 param_spec:
 
 @example
 param_spec:

-             type
-        |    name_list ':' type
-        ;
+  type
+| name_list ':' type
+;

 return_spec:
 return_spec:

-             type
-        |    ID ':' type
-        ;
+  type
+| ID ':' type
+;

 @end example
 
 For a more detailed exposition of LALR(1) parsers and parser
 @end example
 
 For a more detailed exposition of LALR(1) parsers and parser


@@ -7535,10 +7571,11 @@ in the current context, the parse can continue.
 For example:
 
 @example
 For example:
 
 @example

-stmnts:  /* empty string */
-        | stmnts '\n'
-        | stmnts exp '\n'
-        | stmnts error '\n'
+stmnts:
+  /* empty string */
+| stmnts '\n'
+| stmnts exp '\n'
+| stmnts error '\n'

 @end example
 
 The fourth rule in this example says that an error followed by a newline
 @end example
 
 The fourth rule in this example says that an error followed by a newline


@@ -7579,10 +7616,11 @@ close-delimiter will probably appear to be unmatched, and generate another,
 spurious error message:
 
 @example
 spurious error message:
 
 @example

-primary:  '(' expr ')'
-        | '(' error ')'
-        @dots{}
-        ;
+primary:
+  '(' expr ')'
+| '(' error ')'
+@dots{}
+;

 @end example
 
 Error recovery strategies are necessarily guesses.  When they guess wrong,
 @end example
 
 Error recovery strategies are necessarily guesses.  When they guess wrong,


@@ -7704,18 +7742,16 @@ duplication, with actions omitted for brevity:
 @example
 @group
 initdcl:
 @example
 @group
 initdcl:

-          declarator maybeasm '='
-          init
-        | declarator maybeasm
-        ;
+  declarator maybeasm '=' init
+| declarator maybeasm
+;

 @end group
 
 @group
 notype_initdcl:
 @end group
 
 @group
 notype_initdcl:

-          notype_declarator maybeasm '='
-          init
-        | notype_declarator maybeasm
-        ;
+  notype_declarator maybeasm '=' init
+| notype_declarator maybeasm
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -7756,24 +7792,21 @@ as an identifier if it appears in that context.  Here is how you can do it:
 @dots{}
 @end group
 @group
 @dots{}
 @end group
 @group

-expr:   IDENTIFIER
-        | constant
-        | HEX '('
-                @{ hexflag = 1; @}
-          expr ')'
-                @{ hexflag = 0;
-                   $$ = $4; @}
-        | expr '+' expr
-                @{ $$ = make_sum ($1, $3); @}
-        @dots{}
-        ;
+expr:
+  IDENTIFIER
+| constant
+| HEX '('        @{ hexflag = 1; @}
+    expr ')'     @{ hexflag = 0; $$ = $4; @}
+| expr '+' expr  @{ $$ = make_sum ($1, $3); @}
+@dots{}
+;

 @end group
 
 @group
 constant:
 @end group
 
 @group
 constant:

-          INTEGER
-        | STRING
-        ;
+  INTEGER
+| STRING
+;

 @end group
 @end example
 
 @end group
 @end example
 


@@ -7799,12 +7832,12 @@ For example, in C-like languages, a typical error recovery rule is to skip
 tokens until the next semicolon, and then start a new statement, like this:
 
 @example
 tokens until the next semicolon, and then start a new statement, like this:
 
 @example

-stmt:   expr ';'
-        | IF '(' expr ')' stmt @{ @dots{} @}
-        @dots{}
-        error ';'
-                @{ hexflag = 0; @}
-        ;
+stmt:
+  expr ';'
+| IF '(' expr ')' stmt @{ @dots{} @}
+@dots{}
+| error ';'  @{ hexflag = 0; @}
+;

 @end example
 
 If there is a syntax error in the middle of a @samp{hex (@var{expr})}
 @end example
 
 If there is a syntax error in the middle of a @samp{hex (@var{expr})}


@@ -7821,11 +7854,11 @@ and skips to the close-parenthesis:
 
 @example
 @group
 
 @example
 @group

-expr:   @dots{}
-        | '(' expr ')'
-                @{ $$ = $2; @}
-        | '(' error ')'
-        @dots{}
+expr:
+  @dots{}
+| '(' expr ')'   @{ $$ = $2; @}
+| '(' error ')'
+@dots{}

 @end group
 @end example
 
 @end group
 @end example
 


@@ -7883,12 +7916,13 @@ The following grammar file, @file{calc.y}, will be used in the sequel:
 %left '+' '-'
 %left '*'
 %%
 %left '+' '-'
 %left '*'
 %%

-exp: exp '+' exp
-   | exp '-' exp
-   | exp '*' exp
-   | exp '/' exp
-   | NUM
-   ;
+exp:
+  exp '+' exp
+| exp '-' exp
+| exp '*' exp
+| exp '/' exp
+| NUM
+;

 useless: STR;
 %%
 @end example
 useless: STR;
 %%
 @end example


@@ -8359,10 +8393,11 @@ value (from @code{yylval}).
 Here is an example of @code{YYPRINT} suitable for the multi-function
 calculator (@pxref{Mfcalc Declarations, ,Declarations for @code{mfcalc}}):
 
 Here is an example of @code{YYPRINT} suitable for the multi-function
 calculator (@pxref{Mfcalc Declarations, ,Declarations for @code{mfcalc}}):
 

-@smallexample
+@example

 %@{
   static void print_token_value (FILE *, int, YYSTYPE);
 %@{
   static void print_token_value (FILE *, int, YYSTYPE);

-  #define YYPRINT(file, type, value) print_token_value (file, type, value)
+  #define YYPRINT(file, type, value)            \
+    print_token_value (file, type, value)

 %@}
 
 @dots{} %% @dots{} %% @dots{}
 %@}
 
 @dots{} %% @dots{} %% @dots{}


@@ -8375,7 +8410,7 @@ print_token_value (FILE *file, int type, YYSTYPE value)
   else if (type == NUM)
     fprintf (file, "%d", value.val);
 @}
   else if (type == NUM)
     fprintf (file, "%d", value.val);
 @}

-@end smallexample
+@end example

 
 @c ================================================= Invoking Bison
 
 
 @c ================================================= Invoking Bison
 


@@ -8501,7 +8536,7 @@ Also warn about mid-rule values that are used but not set.
 For example, warn about unset @code{$$} in the mid-rule action in:
 
 @example
 For example, warn about unset @code{$$} in the mid-rule action in:
 
 @example

- exp: '1' @{ $1 = 1; @} '+' exp @{ $$ = $2 + $4; @};
+exp: '1' @{ $1 = 1; @} '+' exp @{ $$ = $2 + $4; @};

 @end example
 
 These warnings are not enabled by default since they sometimes prove to
 @end example
 
 These warnings are not enabled by default since they sometimes prove to


@@ -9168,7 +9203,7 @@ the grammar for.
 
 @comment file: calc++-parser.yy
 @example
 
 @comment file: calc++-parser.yy
 @example

-%skeleton "lalr1.cc"                          /*  -*- C++ -*- */
+%skeleton "lalr1.cc" /* -*- C++ -*- */

 %require "@value{VERSION}"
 %defines
 %define parser_class_name "calcxx_parser"
 %require "@value{VERSION}"
 %defines
 %define parser_class_name "calcxx_parser"


@@ -9296,8 +9331,9 @@ The grammar itself is straightforward.
 %start unit;
 unit: assignments exp  @{ driver.result = $2; @};
 
 %start unit;
 unit: assignments exp  @{ driver.result = $2; @};
 

-assignments: assignments assignment @{@}
-           | /* Nothing.  */        @{@};
+assignments:
+  /* Nothing.  */        @{@}
+| assignments assignment @{@};

 
 assignment:
      "identifier" ":=" exp
 
 assignment:
      "identifier" ":=" exp


@@ -9336,7 +9372,7 @@ parser's to get the set of defined tokens.
 
 @comment file: calc++-scanner.ll
 @example
 
 @comment file: calc++-scanner.ll
 @example

-%@{                                            /* -*- C++ -*- */
+%@{ /* -*- C++ -*- */

 # include <cstdlib>
 # include <cerrno>
 # include <climits>
 # include <cstdlib>
 # include <cerrno>
 # include <climits>


@@ -10307,8 +10343,9 @@ real start-symbol:
 @example
 %token START_FOO START_BAR;
 %start start;
 @example
 %token START_FOO START_BAR;
 %start start;

-start: START_FOO foo
-     | START_BAR bar;
+start:
+  START_FOO foo
+| START_BAR bar;

 @end example
 
 These tokens prevents the introduction of new conflicts.  As far as the
 @end example
 
 These tokens prevents the introduction of new conflicts.  As far as the


@@ -11242,7 +11279,7 @@ London, Department of Computer Science, TR-00-12 (December 2000).
 @c LocalWords: NUM exp subsubsection kbd Ctrl ctype EOF getchar isdigit nonfree
 @c LocalWords: ungetc stdin scanf sc calc ulator ls lm cc NEG prec yyerrok rr
 @c LocalWords: longjmp fprintf stderr yylloc YYLTYPE cos ln Stallman Destructor
 @c LocalWords: NUM exp subsubsection kbd Ctrl ctype EOF getchar isdigit nonfree
 @c LocalWords: ungetc stdin scanf sc calc ulator ls lm cc NEG prec yyerrok rr
 @c LocalWords: longjmp fprintf stderr yylloc YYLTYPE cos ln Stallman Destructor

-@c LocalWords: smallexample symrec val tptr FNCT fnctptr func struct sym enum
+@c LocalWords: symrec val tptr FNCT fnctptr func struct sym enum

 @c LocalWords: fnct putsym getsym fname arith fncts atan ptr malloc sizeof Lex
 @c LocalWords: strlen strcpy fctn strcmp isalpha symbuf realloc isalnum DOTDOT
 @c LocalWords: ptypes itype YYPRINT trigraphs yytname expseq vindex dtype Unary
 @c LocalWords: fnct putsym getsym fname arith fncts atan ptr malloc sizeof Lex
 @c LocalWords: strlen strcpy fctn strcmp isalpha symbuf realloc isalnum DOTDOT
 @c LocalWords: ptypes itype YYPRINT trigraphs yytname expseq vindex dtype Unary