Generate the long/short option cross-table.

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index a706a96dad2151e091d141146d36cc2419f800d7..583f48dbef3bc534a0ad16ede33672170fca702b 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -4487,7 +4487,7 @@ may override this restriction with the @code{%start} declaration as follows:
 @subsection A Pure (Reentrant) Parser
 @cindex reentrant parser
 @cindex pure parser
 @subsection A Pure (Reentrant) Parser
 @cindex reentrant parser
 @cindex pure parser

-@findex %pure-parser
+@findex %define api.pure

 
 A @dfn{reentrant} program is one which does not alter in the course of
 execution; in other words, it consists entirely of @dfn{pure} (read-only)
 
 A @dfn{reentrant} program is one which does not alter in the course of
 execution; in other words, it consists entirely of @dfn{pure} (read-only)


@@ -4503,19 +4503,19 @@ statically allocated variables for communication with @code{yylex},
 including @code{yylval} and @code{yylloc}.)
 
 Alternatively, you can generate a pure, reentrant parser.  The Bison
 including @code{yylval} and @code{yylloc}.)
 
 Alternatively, you can generate a pure, reentrant parser.  The Bison

-declaration @code{%pure-parser} says that you want the parser to be
+declaration @code{%define api.pure} says that you want the parser to be

 reentrant.  It looks like this:
 
 @example
 reentrant.  It looks like this:
 
 @example

-%pure-parser
+%define api.pure

 @end example
 
 The result is that the communication variables @code{yylval} and
 @code{yylloc} become local variables in @code{yyparse}, and a different
 calling convention is used for the lexical analyzer function
 @code{yylex}.  @xref{Pure Calling, ,Calling Conventions for Pure
 @end example
 
 The result is that the communication variables @code{yylval} and
 @code{yylloc} become local variables in @code{yyparse}, and a different
 calling convention is used for the lexical analyzer function
 @code{yylex}.  @xref{Pure Calling, ,Calling Conventions for Pure

-Parsers}, for the details of this.  The variable @code{yynerrs} 
-becomes local in @code{yyparse} in pull mode but it becomes a member 
+Parsers}, for the details of this.  The variable @code{yynerrs}
+becomes local in @code{yyparse} in pull mode but it becomes a member

 of yypstate in push mode.  (@pxref{Error Reporting, ,The Error
 Reporting Function @code{yyerror}}).  The convention for calling
 @code{yyparse} itself is unchanged.
 of yypstate in push mode.  (@pxref{Error Reporting, ,The Error
 Reporting Function @code{yyerror}}).  The convention for calling
 @code{yyparse} itself is unchanged.


@@ -4528,47 +4528,47 @@ valid grammar.
 @subsection A Push Parser
 @cindex push parser
 @cindex push parser
 @subsection A Push Parser
 @cindex push parser
 @cindex push parser

-@findex %define push_pull
+@findex %define api.push_pull

 
 

-A pull parser is called once and it takes control until all its input 
-is completely parsed.  A push parser, on the other hand, is called 
+A pull parser is called once and it takes control until all its input
+is completely parsed.  A push parser, on the other hand, is called

 each time a new token is made available.
 
 each time a new token is made available.
 

-A push parser is typically useful when the parser is part of a 
+A push parser is typically useful when the parser is part of a

 main event loop in the client's application.  This is typically
 main event loop in the client's application.  This is typically

-a requirement of a GUI, when the main event loop needs to be triggered 
-within a certain time period.  
+a requirement of a GUI, when the main event loop needs to be triggered
+within a certain time period.

 
 Normally, Bison generates a pull parser.
 The following Bison declaration says that you want the parser to be a push
 
 Normally, Bison generates a pull parser.
 The following Bison declaration says that you want the parser to be a push

-parser (@pxref{Decl Summary,,%define push_pull}):
+parser (@pxref{Decl Summary,,%define api.push_pull}):

 
 @example
 
 @example

-%define push_pull "push"
+%define api.push_pull "push"

 @end example
 
 In almost all cases, you want to ensure that your push parser is also
 a pure parser (@pxref{Pure Decl, ,A Pure (Reentrant) Parser}).  The only
 @end example
 
 In almost all cases, you want to ensure that your push parser is also
 a pure parser (@pxref{Pure Decl, ,A Pure (Reentrant) Parser}).  The only

-time you should create an impure push parser is to have backwards 
+time you should create an impure push parser is to have backwards

 compatibility with the impure Yacc pull mode interface.  Unless you know
 what you are doing, your declarations should look like this:
 
 @example
 compatibility with the impure Yacc pull mode interface.  Unless you know
 what you are doing, your declarations should look like this:
 
 @example

-%pure-parser
-%define push_pull "push"
+%define api.pure
+%define api.push_pull "push"

 @end example
 
 @end example
 

-There is a major notable functional difference between the pure push parser 
-and the impure push parser.  It is acceptable for a pure push parser to have 
+There is a major notable functional difference between the pure push parser
+and the impure push parser.  It is acceptable for a pure push parser to have

 many parser instances, of the same type of parser, in memory at the same time.
 An impure push parser should only use one parser at a time.
 
 When a push parser is selected, Bison will generate some new symbols in
 many parser instances, of the same type of parser, in memory at the same time.
 An impure push parser should only use one parser at a time.
 
 When a push parser is selected, Bison will generate some new symbols in

-the generated parser.  @code{yypstate} is a structure that the generated 
-parser uses to store the parser's state.  @code{yypstate_new} is the 
+the generated parser.  @code{yypstate} is a structure that the generated
+parser uses to store the parser's state.  @code{yypstate_new} is the

 function that will create a new parser instance.  @code{yypstate_delete}
 will free the resources associated with the corresponding parser instance.
 function that will create a new parser instance.  @code{yypstate_delete}
 will free the resources associated with the corresponding parser instance.

-Finally, @code{yypush_parse} is the function that should be called whenever a 
+Finally, @code{yypush_parse} is the function that should be called whenever a

 token is available to provide the parser.  A trivial example
 of using a pure push parser would look like this:
 
 token is available to provide the parser.  A trivial example
 of using a pure push parser would look like this:
 


@@ -4582,10 +4582,10 @@ yypstate_delete (ps);
 @end example
 
 If the user decided to use an impure push parser, a few things about
 @end example
 
 If the user decided to use an impure push parser, a few things about

-the generated parser will change.  The @code{yychar} variable becomes 
+the generated parser will change.  The @code{yychar} variable becomes

 a global variable instead of a variable in the @code{yypush_parse} function.
 For this reason, the signature of the @code{yypush_parse} function is
 a global variable instead of a variable in the @code{yypush_parse} function.
 For this reason, the signature of the @code{yypush_parse} function is

-changed to remove the token as a parameter.  A nonreentrant push parser 
+changed to remove the token as a parameter.  A nonreentrant push parser

 example would thus look like this:
 
 @example
 example would thus look like this:
 
 @example


@@ -4599,26 +4599,26 @@ do @{
 yypstate_delete (ps);
 @end example
 
 yypstate_delete (ps);
 @end example
 

-That's it. Notice the next token is put into the global variable @code{yychar} 
+That's it. Notice the next token is put into the global variable @code{yychar}

 for use by the next invocation of the @code{yypush_parse} function.
 
 for use by the next invocation of the @code{yypush_parse} function.
 

-Bison also supports both the push parser interface along with the pull parser 
+Bison also supports both the push parser interface along with the pull parser

 interface in the same generated parser.  In order to get this functionality,
 interface in the same generated parser.  In order to get this functionality,

-you should replace the @code{%define push_pull "push"} declaration with the 
-@code{%define push_pull "both"} declaration.  Doing this will create all of the 
-symbols mentioned earlier along with the two extra symbols, @code{yyparse} 
-and @code{yypull_parse}.  @code{yyparse} can be used exactly as it normally 
-would be used.  However, the user should note that it is implemented in the 
+you should replace the @code{%define api.push_pull "push"} declaration with the
+@code{%define api.push_pull "both"} declaration.  Doing this will create all of
+the symbols mentioned earlier along with the two extra symbols, @code{yyparse}
+and @code{yypull_parse}.  @code{yyparse} can be used exactly as it normally
+would be used.  However, the user should note that it is implemented in the

 generated parser by calling @code{yypull_parse}.
 This makes the @code{yyparse} function that is generated with the
 generated parser by calling @code{yypull_parse}.
 This makes the @code{yyparse} function that is generated with the

-@code{%define push_pull "both"} declaration slower than the normal
+@code{%define api.push_pull "both"} declaration slower than the normal

 @code{yyparse} function.  If the user
 calls the @code{yypull_parse} function it will parse the rest of the input
 @code{yyparse} function.  If the user
 calls the @code{yypull_parse} function it will parse the rest of the input

-stream.  It is possible to @code{yypush_parse} tokens to select a subgrammar 
-and then @code{yypull_parse} the rest of the input stream.  If you would like 
-to switch back and forth between between parsing styles, you would have to 
-write your own @code{yypull_parse} function that knows when to quit looking 
-for input.  An example of using the @code{yypull_parse} function would look 
+stream.  It is possible to @code{yypush_parse} tokens to select a subgrammar
+and then @code{yypull_parse} the rest of the input stream.  If you would like
+to switch back and forth between between parsing styles, you would have to
+write your own @code{yypull_parse} function that knows when to quit looking
+for input.  An example of using the @code{yypull_parse} function would look

 like this:
 
 @example
 like this:
 
 @example


@@ -4627,9 +4627,9 @@ yypull_parse (ps); /* Will call the lexer */
 yypstate_delete (ps);
 @end example
 
 yypstate_delete (ps);
 @end example
 

-Adding the @code{%pure-parser} declaration does exactly the same thing to the 
-generated parser with @code{%define push_pull "both"} as it did for 
-@code{%define push_pull "push"}.
+Adding the @code{%define api.pure} declaration does exactly the same thing to
+the generated parser with @code{%define api.push_pull "both"} as it did for
+@code{%define api.push_pull "push"}.

 
 @node Decl Summary
 @subsection Bison Declaration Summary
 
 @node Decl Summary
 @subsection Bison Declaration Summary


@@ -4837,8 +4837,22 @@ target language and/or parser skeleton.
 Some of the accepted @var{variable}s are:
 
 @itemize @bullet
 Some of the accepted @var{variable}s are:
 
 @itemize @bullet

-@item push_pull
-@findex %define push_pull
+@item api.pure
+@findex %define api.pure
+
+@itemize @bullet
+@item Language(s): C
+
+@item Purpose: Request a pure (reentrant) parser program.
+@xref{Pure Decl, ,A Pure (Reentrant) Parser}.
+
+@item Accepted Values: Boolean
+
+@item Default Value: @code{"false"}
+@end itemize
+
+@item api.push_pull
+@findex %define api.push_pull

 
 @itemize @bullet
 @item Language(s): C (LALR(1) only)
 
 @itemize @bullet
 @item Language(s): C (LALR(1) only)


@@ -5022,10 +5036,10 @@ Rename the external symbols used in the parser so that they start with
 in C parsers
 is @code{yyparse}, @code{yylex}, @code{yyerror}, @code{yynerrs},
 @code{yylval}, @code{yychar}, @code{yydebug}, and
 in C parsers
 is @code{yyparse}, @code{yylex}, @code{yyerror}, @code{yynerrs},
 @code{yylval}, @code{yychar}, @code{yydebug}, and

-(if locations are used) @code{yylloc}.  If you use a push parser, 
-@code{yypush_parse}, @code{yypull_parse}, @code{yypstate}, 
-@code{yypstate_new} and @code{yypstate_delete} will 
-also be renamed.  For example, if you use @samp{%name-prefix "c_"}, the 
+(if locations are used) @code{yylloc}.  If you use a push parser,
+@code{yypush_parse}, @code{yypull_parse}, @code{yypstate},
+@code{yypstate_new} and @code{yypstate_delete} will
+also be renamed.  For example, if you use @samp{%name-prefix "c_"}, the

 names become @code{c_parse}, @code{c_lex}, and so on.
 For C++ parsers, see the @code{%define namespace} documentation in this
 section.
 names become @code{c_parse}, @code{c_lex}, and so on.
 For C++ parsers, see the @code{%define namespace} documentation in this
 section.


@@ -5054,8 +5068,8 @@ Specify @var{file} for the parser file.
 @end deffn
 
 @deffn {Directive} %pure-parser
 @end deffn
 
 @deffn {Directive} %pure-parser

-Request a pure (reentrant) parser program (@pxref{Pure Decl, ,A Pure
-(Reentrant) Parser}).
+Deprecated version of @code{%define api.pure} (@pxref{Decl Summary, ,%define}),
+for which Bison is more careful to warn about unreasonable usage.

 @end deffn
 
 @deffn {Directive} %require "@var{version}"
 @end deffn
 
 @deffn {Directive} %require "@var{version}"


@@ -5141,10 +5155,10 @@ names that do not conflict.
 
 The precise list of symbols renamed is @code{yyparse}, @code{yylex},
 @code{yyerror}, @code{yynerrs}, @code{yylval}, @code{yylloc},
 
 The precise list of symbols renamed is @code{yyparse}, @code{yylex},
 @code{yyerror}, @code{yynerrs}, @code{yylval}, @code{yylloc},

-@code{yychar} and @code{yydebug}.  If you use a push parser, 
-@code{yypush_parse}, @code{yypull_parse}, @code{yypstate}, 
+@code{yychar} and @code{yydebug}.  If you use a push parser,
+@code{yypush_parse}, @code{yypull_parse}, @code{yypstate},

 @code{yypstate_new} and @code{yypstate_delete} will also be renamed.
 @code{yypstate_new} and @code{yypstate_delete} will also be renamed.

-For example, if you use @samp{-p c}, the names become @code{cparse}, 
+For example, if you use @samp{-p c}, the names become @code{cparse},

 @code{clex}, and so on.
 
 @strong{All the other variables and macros associated with Bison are not
 @code{clex}, and so on.
 
 @strong{All the other variables and macros associated with Bison are not


@@ -5176,9 +5190,9 @@ in the grammar file, you are likely to run into trouble.
 * Parser Function::   How to call @code{yyparse} and what it returns.
 * Push Parser Function::  How to call @code{yypush_parse} and what it returns.
 * Pull Parser Function::  How to call @code{yypull_parse} and what it returns.
 * Parser Function::   How to call @code{yyparse} and what it returns.
 * Push Parser Function::  How to call @code{yypush_parse} and what it returns.
 * Pull Parser Function::  How to call @code{yypull_parse} and what it returns.

-* Parser Create Function::  How to call @code{yypstate_new} and what it 
+* Parser Create Function::  How to call @code{yypstate_new} and what it

                         returns.
                         returns.

-* Parser Delete Function::  How to call @code{yypstate_delete} and what it 
+* Parser Delete Function::  How to call @code{yypstate_delete} and what it

                         returns.
 * Lexical::           You must supply a function @code{yylex}
                         which reads tokens.
                         returns.
 * Lexical::           You must supply a function @code{yylex}
                         which reads tokens.


@@ -5266,13 +5280,13 @@ exp: @dots{}    @{ @dots{}; *randomness += 1; @dots{} @}
 @section The Push Parser Function @code{yypush_parse}
 @findex yypush_parse
 
 @section The Push Parser Function @code{yypush_parse}
 @findex yypush_parse
 

-You call the function @code{yypush_parse} to parse a single token.  This 
-function is available if either the @code{%define push_pull "push"} or 
-@code{%define push_pull "both"} declaration is used.  
+You call the function @code{yypush_parse} to parse a single token.  This
+function is available if either the @code{%define api.push_pull "push"} or
+@code{%define api.push_pull "both"} declaration is used.

 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun int yypush_parse (yypstate *yyps)
 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun int yypush_parse (yypstate *yyps)

-The value returned by @code{yypush_parse} is the same as for yyparse with the 
+The value returned by @code{yypush_parse} is the same as for yyparse with the

 following exception.  @code{yypush_parse} will return YYPUSH_MORE if more input
 is required to finish parsing the grammar.
 @end deftypefun
 following exception.  @code{yypush_parse} will return YYPUSH_MORE if more input
 is required to finish parsing the grammar.
 @end deftypefun


@@ -5281,9 +5295,9 @@ is required to finish parsing the grammar.
 @section The Pull Parser Function @code{yypull_parse}
 @findex yypull_parse
 
 @section The Pull Parser Function @code{yypull_parse}
 @findex yypull_parse
 

-You call the function @code{yypull_parse} to parse the rest of the input 
-stream.  This function is available if the @code{%define push_pull "both"} 
-declaration is used.  
+You call the function @code{yypull_parse} to parse the rest of the input
+stream.  This function is available if the @code{%define api.push_pull "both"}
+declaration is used.

 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun int yypull_parse (yypstate *yyps)
 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun int yypull_parse (yypstate *yyps)


@@ -5294,9 +5308,9 @@ The value returned by @code{yypull_parse} is the same as for @code{yyparse}.
 @section The Parser Create Function @code{yystate_new}
 @findex yypstate_new
 
 @section The Parser Create Function @code{yystate_new}
 @findex yypstate_new
 

-You call the function @code{yypstate_new} to create a new parser instance.  
-This function is available if either the @code{%define push_pull "push"} or 
-@code{%define push_pull "both"} declaration is used.  
+You call the function @code{yypstate_new} to create a new parser instance.
+This function is available if either the @code{%define api.push_pull "push"} or
+@code{%define api.push_pull "both"} declaration is used.

 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun yypstate *yypstate_new (void)
 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun yypstate *yypstate_new (void)


@@ -5309,8 +5323,8 @@ or NULL if no memory was available.
 @findex yypstate_delete
 
 You call the function @code{yypstate_delete} to delete a parser instance.
 @findex yypstate_delete
 
 You call the function @code{yypstate_delete} to delete a parser instance.

-function is available if either the @code{%define push_pull "push"} or 
-@code{%define push_pull "both"} declaration is used.  
+function is available if either the @code{%define api.push_pull "push"} or
+@code{%define api.push_pull "both"} declaration is used.

 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun void yypstate_delete (yypstate *yyps)
 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun void yypstate_delete (yypstate *yyps)


@@ -5498,7 +5512,7 @@ The data type of @code{yylloc} has the name @code{YYLTYPE}.
 @node Pure Calling
 @subsection Calling Conventions for Pure Parsers
 
 @node Pure Calling
 @subsection Calling Conventions for Pure Parsers
 

-When you use the Bison declaration @code{%pure-parser} to request a
+When you use the Bison declaration @code{%define api.pure} to request a

 pure, reentrant parser, the global communication variables @code{yylval}
 and @code{yylloc} cannot be used.  (@xref{Pure Decl, ,A Pure (Reentrant)
 Parser}.)  In such parsers the two global variables are replaced by
 pure, reentrant parser, the global communication variables @code{yylval}
 and @code{yylloc} cannot be used.  (@xref{Pure Decl, ,A Pure (Reentrant)
 Parser}.)  In such parsers the two global variables are replaced by


@@ -5549,7 +5563,7 @@ int yylex   (int *nastiness);
 int yyparse (int *nastiness, int *randomness);
 @end example
 
 int yyparse (int *nastiness, int *randomness);
 @end example
 

-If @code{%pure-parser} is added:
+If @code{%define api.pure} is added:

 
 @example
 int yylex   (YYSTYPE *lvalp, int *nastiness);
 
 @example
 int yylex   (YYSTYPE *lvalp, int *nastiness);


@@ -5557,7 +5571,7 @@ int yyparse (int *nastiness, int *randomness);
 @end example
 
 @noindent
 @end example
 
 @noindent

-and finally, if both @code{%pure-parser} and @code{%locations} are used:
+and finally, if both @code{%define api.pure} and @code{%locations} are used:

 
 @example
 int yylex   (YYSTYPE *lvalp, YYLTYPE *llocp, int *nastiness);
 
 @example
 int yylex   (YYSTYPE *lvalp, YYLTYPE *llocp, int *nastiness);


@@ -5623,7 +5637,7 @@ Obviously, in location tracking pure parsers, @code{yyerror} should have
 an access to the current location.
 This is indeed the case for the @acronym{GLR}
 parsers, but not for the Yacc parser, for historical reasons.  I.e., if
 an access to the current location.
 This is indeed the case for the @acronym{GLR}
 parsers, but not for the Yacc parser, for historical reasons.  I.e., if

-@samp{%locations %pure-parser} is passed then the prototypes for
+@samp{%locations %define api.pure} is passed then the prototypes for

 @code{yyerror} are:
 
 @example
 @code{yyerror} are:
 
 @example


@@ -5641,13 +5655,14 @@ void yyerror (int *nastiness, char const *msg);  /* GLR parsers.   */
 Finally, @acronym{GLR} and Yacc parsers share the same @code{yyerror} calling
 convention for absolutely pure parsers, i.e., when the calling
 convention of @code{yylex} @emph{and} the calling convention of
 Finally, @acronym{GLR} and Yacc parsers share the same @code{yyerror} calling
 convention for absolutely pure parsers, i.e., when the calling
 convention of @code{yylex} @emph{and} the calling convention of

-@code{%pure-parser} are pure.  I.e.:
+@code{%define api.pure} are pure.
+I.e.:

 
 @example
 /* Location tracking.  */
 %locations
 /* Pure yylex.  */
 
 @example
 /* Location tracking.  */
 %locations
 /* Pure yylex.  */

-%pure-parser
+%define api.pure

 %lex-param   @{int *nastiness@}
 /* Pure yyparse.  */
 %parse-param @{int *nastiness@}
 %lex-param   @{int *nastiness@}
 /* Pure yyparse.  */
 %parse-param @{int *nastiness@}


@@ -7846,20 +7861,7 @@ the corresponding short option.
 
 @multitable {@option{--defines=@var{defines-file}}} {@option{-b @var{file-prefix}XXX}}
 @headitem Long Option @tab Short Option
 
 @multitable {@option{--defines=@var{defines-file}}} {@option{-b @var{file-prefix}XXX}}
 @headitem Long Option @tab Short Option

-@item @option{--debug}                      @tab @option{-t}
-@item @option{--defines=@var{defines-file}} @tab @option{-d}
-@item @option{--file-prefix=@var{prefix}}   @tab @option{-b @var{file-prefix}}
-@item @option{--graph=@var{graph-file}}     @tab @option{-d}
-@item @option{--help}                       @tab @option{-h}
-@item @option{--name-prefix=@var{prefix}}   @tab @option{-p @var{name-prefix}}
-@item @option{--no-lines}                   @tab @option{-l}
-@item @option{--output=@var{outfile}}       @tab @option{-o @var{outfile}}
-@item @option{--print-localedir}            @tab
-@item @option{--print-datadir}              @tab
-@item @option{--token-table}                @tab @option{-k}
-@item @option{--verbose}                    @tab @option{-v}
-@item @option{--version}                    @tab @option{-V}
-@item @option{--yacc}                       @tab @option{-y}
+@include cross-options.texi

 @end multitable
 
 @node Yacc Library
 @end multitable
 
 @node Yacc Library


@@ -8108,7 +8110,7 @@ described by @var{m}.
 
 The parser invokes the scanner by calling @code{yylex}.  Contrary to C
 parsers, C++ parsers are always pure: there is no point in using the
 
 The parser invokes the scanner by calling @code{yylex}.  Contrary to C
 parsers, C++ parsers are always pure: there is no point in using the

-@code{%pure-parser} directive.  Therefore the interface is as follows.
+@code{%define api.pure} directive.  Therefore the interface is as follows.

 
 @deftypemethod {parser} {int} yylex (semantic_value_type& @var{yylval}, location_type& @var{yylloc}, @var{type1} @var{arg1}, ...)
 Return the next token.  Its type is the return value, its semantic
 
 @deftypemethod {parser} {int} yylex (semantic_value_type& @var{yylval}, location_type& @var{yylloc}, @var{type1} @var{arg1}, ...)
 Return the next token.  Its type is the return value, its semantic


@@ -8860,10 +8862,9 @@ The return type can be changed using @samp{%define "stype"
 @end deftypemethod
 
 
 @end deftypemethod
 
 

-If @code{%pure-parser} is not specified, the lexer interface
-resides in the same class (@code{YYParser}) as the Bison-generated
-parser. The fields and methods that are provided to
-this end are as follows.
+The lexer interface resides in the same class (@code{YYParser}) as the
+Bison-generated parser.
+The fields and methods that are provided to this end are as follows.

 
 @deftypemethod {YYParser} {void} error (Location @var{l}, String @var{m})
 As explained in @pxref{Java Parser Interface}, this method is defined
 
 @deftypemethod {YYParser} {void} error (Location @var{l}, String @var{m})
 As explained in @pxref{Java Parser Interface}, this method is defined


@@ -8996,7 +8997,7 @@ or
 @display
 My parser includes support for an @samp{#include}-like feature, in
 which case I run @code{yyparse} from @code{yyparse}.  This fails
 @display
 My parser includes support for an @samp{#include}-like feature, in
 which case I run @code{yyparse} from @code{yyparse}.  This fails

-although I did specify I needed a @code{%pure-parser}.
+although I did specify @code{%define api.pure}.

 @end display
 
 These problems typically come not from Bison itself, but from
 @end display
 
 These problems typically come not from Bison itself, but from


@@ -9558,8 +9559,8 @@ Bison declaration to assign a precedence to a specific rule.
 @end deffn
 
 @deffn {Directive} %pure-parser
 @end deffn
 
 @deffn {Directive} %pure-parser

-Bison declaration to request a pure (reentrant) parser.
-@xref{Pure Decl, ,A Pure (Reentrant) Parser}.
+Deprecated version of @code{%define api.pure} (@pxref{Decl Summary, ,%define}),
+for which Bison is more careful to warn about unreasonable usage.

 @end deffn
 
 @deffn {Directive} %require "@var{version}"
 @end deffn
 
 @deffn {Directive} %require "@var{version}"


@@ -9736,7 +9737,7 @@ Management}.
 
 @deffn {Variable} yynerrs
 Global variable which Bison increments each time it reports a syntax error.
 
 @deffn {Variable} yynerrs
 Global variable which Bison increments each time it reports a syntax error.

-(In a pure parser, it is a local variable within @code{yyparse}. In a 
+(In a pure parser, it is a local variable within @code{yyparse}. In a

 pure push parser, it is a member of yypstate.)
 @xref{Error Reporting, ,The Error Reporting Function @code{yyerror}}.
 @end deffn
 pure push parser, it is a member of yypstate.)
 @xref{Error Reporting, ,The Error Reporting Function @code{yyerror}}.
 @end deffn


@@ -9747,29 +9748,29 @@ parsing.  @xref{Parser Function, ,The Parser Function @code{yyparse}}.
 @end deffn
 
 @deffn {Function} yypstate_delete
 @end deffn
 
 @deffn {Function} yypstate_delete

-The function to delete a parser instance, produced by Bison in push mode; 
+The function to delete a parser instance, produced by Bison in push mode;

 call this function to delete the memory associated with a parser.
 call this function to delete the memory associated with a parser.

-@xref{Parser Delete Function, ,The Parser Delete Function 
+@xref{Parser Delete Function, ,The Parser Delete Function

 @code{yypstate_delete}}.
 @end deffn
 
 @deffn {Function} yypstate_new
 @code{yypstate_delete}}.
 @end deffn
 
 @deffn {Function} yypstate_new

-The function to create a parser instance, produced by Bison in push mode; 
+The function to create a parser instance, produced by Bison in push mode;

 call this function to create a new parser.
 call this function to create a new parser.

-@xref{Parser Create Function, ,The Parser Create Function 
+@xref{Parser Create Function, ,The Parser Create Function

 @code{yypstate_new}}.
 @end deffn
 
 @deffn {Function} yypull_parse
 @code{yypstate_new}}.
 @end deffn
 
 @deffn {Function} yypull_parse

-The parser function produced by Bison in push mode; call this function to 
-parse the rest of the input stream.  
-@xref{Pull Parser Function, ,The Pull Parser Function 
+The parser function produced by Bison in push mode; call this function to
+parse the rest of the input stream.
+@xref{Pull Parser Function, ,The Pull Parser Function

 @code{yypull_parse}}.
 @end deffn
 
 @deffn {Function} yypush_parse
 @code{yypull_parse}}.
 @end deffn
 
 @deffn {Function} yypush_parse

-The parser function produced by Bison in push mode; call this function to 
-parse a single token.  @xref{Push Parser Function, ,The Push Parser Function 
+The parser function produced by Bison in push mode; call this function to
+parse a single token.  @xref{Push Parser Function, ,The Push Parser Function

 @code{yypush_parse}}.
 @end deffn
 
 @code{yypush_parse}}.
 @end deffn