Define make_symbol in the header.

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 3ba5b652a2c4b63d0fcefdcd32a093b300849c5c..70f62672a223abf88609df4c6e4280426568554a 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -30,11 +30,12 @@
 
 @copying
 
 
 @copying
 

-This manual is for @acronym{GNU} Bison (version @value{VERSION},
-@value{UPDATED}), the @acronym{GNU} parser generator.
+This manual (@value{UPDATED}) is for @acronym{GNU} Bison (version
+@value{VERSION}), the @acronym{GNU} parser generator.

 
 Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1995, 1998,
 
 Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1995, 1998,

-1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
+1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software
+Foundation, Inc.

 
 @quotation
 Permission is granted to copy, distribute and/or modify this document
 
 @quotation
 Permission is granted to copy, distribute and/or modify this document


@@ -45,10 +46,10 @@ being ``A @acronym{GNU} Manual,'' and with the Back-Cover Texts as in
 (a) below.  A copy of the license is included in the section entitled
 ``@acronym{GNU} Free Documentation License.''
 
 (a) below.  A copy of the license is included in the section entitled
 ``@acronym{GNU} Free Documentation License.''
 

-(a) The @acronym{FSF}'s Back-Cover Text is: ``You have freedom to copy
-and modify this @acronym{GNU} Manual, like @acronym{GNU} software.
-Copies published by the Free Software Foundation raise funds for
-@acronym{GNU} development.''
+(a) The FSF's Back-Cover Text is: ``You have the freedom to copy and
+modify this @acronym{GNU} manual.  Buying copies from the @acronym{FSF}
+supports it in developing @acronym{GNU} and promoting software
+freedom.''

 @end quotation
 @end copying
 
 @end quotation
 @end copying
 


@@ -263,7 +264,8 @@ The Bison Parser Algorithm
 Operator Precedence
 
 * Why Precedence::    An example showing why precedence is needed.
 Operator Precedence
 
 * Why Precedence::    An example showing why precedence is needed.

-* Using Precedence::  How to specify precedence in Bison grammars.
+* Using Precedence::  How to specify precedence and associativity.
+* Precedence Only::   How to specify precedence only.

 * Precedence Examples::  How these features are used in the previous example.
 * How Precedence::    How they work.
 
 * Precedence Examples::  How these features are used in the previous example.
 * How Precedence::    How they work.
 


@@ -314,8 +316,10 @@ Java Parsers
 * Java Semantic Values::         %type and %token vs. Java
 * Java Location Values::         The position and location classes
 * Java Parser Interface::        Instantiating and running the parser
 * Java Semantic Values::         %type and %token vs. Java
 * Java Location Values::         The position and location classes
 * Java Parser Interface::        Instantiating and running the parser

-* Java Scanner Interface::       Java scanners, and pure parsers
+* Java Scanner Interface::       Specifying the scanner for the parser
+* Java Action Features::         Special features for use in actions.

 * Java Differences::             Differences between C/C++ and Java Grammars
 * Java Differences::             Differences between C/C++ and Java Grammars

+* Java Declarations Summary::    List of Bison declarations used with Java

 
 Frequently Asked Questions
 
 
 Frequently Asked Questions
 


@@ -1855,8 +1859,8 @@ parentheses nested to arbitrary depth.  Here is the Bison code for
 %token NUM
 %left '-' '+'
 %left '*' '/'
 %token NUM
 %left '-' '+'
 %left '*' '/'

-%left NEG     /* negation--unary minus */
-%right '^'    /* exponentiation */
+%precedence NEG   /* negation--unary minus */
+%right '^'        /* exponentiation */

 
 %% /* The grammar follows.  */
 input:    /* empty */
 
 %% /* The grammar follows.  */
 input:    /* empty */


@@ -1889,15 +1893,16 @@ In the second section (Bison declarations), @code{%left} declares token
 types and says they are left-associative operators.  The declarations
 @code{%left} and @code{%right} (right associativity) take the place of
 @code{%token} which is used to declare a token type name without
 types and says they are left-associative operators.  The declarations
 @code{%left} and @code{%right} (right associativity) take the place of
 @code{%token} which is used to declare a token type name without

-associativity.  (These tokens are single-character literals, which
+associativity/precedence.  (These tokens are single-character literals, which

 ordinarily don't need to be declared.  We declare them here to specify
 ordinarily don't need to be declared.  We declare them here to specify

-the associativity.)
+the associativity/precedence.)

 
 Operator precedence is determined by the line ordering of the
 declarations; the higher the line number of the declaration (lower on
 the page or screen), the higher the precedence.  Hence, exponentiation
 has the highest precedence, unary minus (@code{NEG}) is next, followed
 
 Operator precedence is determined by the line ordering of the
 declarations; the higher the line number of the declaration (lower on
 the page or screen), the higher the precedence.  Hence, exponentiation
 has the highest precedence, unary minus (@code{NEG}) is next, followed

-by @samp{*} and @samp{/}, and so on.  @xref{Precedence, ,Operator
+by @samp{*} and @samp{/}, and so on.  Unary minus is not associative,
+only precedence matters (@code{%precedence}. @xref{Precedence, ,Operator

 Precedence}.
 
 The other important new feature is the @code{%prec} in the grammar
 Precedence}.
 
 The other important new feature is the @code{%prec} in the grammar


@@ -2000,7 +2005,7 @@ the same as the declarations for the infix notation calculator.
 
 %left '-' '+'
 %left '*' '/'
 
 %left '-' '+'
 %left '*' '/'

-%left NEG
+%precedence NEG

 %right '^'
 
 %% /* The grammar follows.  */
 %right '^'
 
 %% /* The grammar follows.  */


@@ -2248,8 +2253,8 @@ Here are the C and Bison declarations for the multi-function calculator.
 %right '='
 %left '-' '+'
 %left '*' '/'
 %right '='
 %left '-' '+'
 %left '*' '/'

-%left NEG     /* negation--unary minus */
-%right '^'    /* exponentiation */
+%precedence NEG /* negation--unary minus */
+%right '^'      /* exponentiation */

 @end group
 %% /* The grammar follows.  */
 @end smallexample
 @end group
 %% /* The grammar follows.  */
 @end smallexample


@@ -4016,13 +4021,14 @@ Bison will convert this into a @code{#define} directive in
 the parser, so that the function @code{yylex} (if it is in this file)
 can use the name @var{name} to stand for this token type's code.
 
 the parser, so that the function @code{yylex} (if it is in this file)
 can use the name @var{name} to stand for this token type's code.
 

-Alternatively, you can use @code{%left}, @code{%right}, or
+Alternatively, you can use @code{%left}, @code{%right},
+@code{%precedence}, or

 @code{%nonassoc} instead of @code{%token}, if you wish to specify
 associativity and precedence.  @xref{Precedence Decl, ,Operator
 Precedence}.
 
 You can explicitly specify the numeric code for a token type by appending
 @code{%nonassoc} instead of @code{%token}, if you wish to specify
 associativity and precedence.  @xref{Precedence Decl, ,Operator
 Precedence}.
 
 You can explicitly specify the numeric code for a token type by appending

-a decimal or hexadecimal integer value in the field immediately
+a nonnegative decimal or hexadecimal integer value in the field immediately

 following the token name:
 
 @example
 following the token name:
 
 @example


@@ -4075,6 +4081,16 @@ Once you equate the literal string and the token name, you can use them
 interchangeably in further declarations or the grammar rules.  The
 @code{yylex} function can use the token name or the literal string to
 obtain the token type code number (@pxref{Calling Convention}).
 interchangeably in further declarations or the grammar rules.  The
 @code{yylex} function can use the token name or the literal string to
 obtain the token type code number (@pxref{Calling Convention}).

+Syntax error messages passed to @code{yyerror} from the parser will reference
+the literal string instead of the token name.
+
+The token numbered as 0 corresponds to end of file; the following line
+allows for nicer error messages referring to ``end of file'' instead
+of ``$end'':
+
+@example
+%token END 0 "end of file"
+@end example

 
 @node Precedence Decl
 @subsection Operator Precedence
 
 @node Precedence Decl
 @subsection Operator Precedence


@@ -4082,13 +4098,14 @@ obtain the token type code number (@pxref{Calling Convention}).
 @cindex declaring operator precedence
 @cindex operator precedence, declaring
 
 @cindex declaring operator precedence
 @cindex operator precedence, declaring
 

-Use the @code{%left}, @code{%right} or @code{%nonassoc} declaration to
+Use the @code{%left}, @code{%right}, @code{%nonassoc}, or
+@code{%precedence} declaration to

 declare a token and specify its precedence and associativity, all at
 once.  These are called @dfn{precedence declarations}.
 @xref{Precedence, ,Operator Precedence}, for general information on
 operator precedence.
 
 declare a token and specify its precedence and associativity, all at
 once.  These are called @dfn{precedence declarations}.
 @xref{Precedence, ,Operator Precedence}, for general information on
 operator precedence.
 

-The syntax of a precedence declaration is the same as that of
+The syntax of a precedence declaration is nearly the same as that of

 @code{%token}: either
 
 @example
 @code{%token}: either
 
 @example


@@ -4118,6 +4135,10 @@ left-associativity (grouping @var{x} with @var{y} first) and
 means that @samp{@var{x} @var{op} @var{y} @var{op} @var{z}} is
 considered a syntax error.
 
 means that @samp{@var{x} @var{op} @var{y} @var{op} @var{z}} is
 considered a syntax error.
 

+@code{%precedence} gives only precedence to the @var{symbols}, and
+defines no associativity at all.  Use this to define precedence only,
+and leave any potential conflict due to associativity enabled.
+

 @item
 The precedence of an operator determines how it nests with other operators.
 All the tokens declared in a single precedence declaration have equal
 @item
 The precedence of an operator determines how it nests with other operators.
 All the tokens declared in a single precedence declaration have equal


@@ -4126,6 +4147,18 @@ When two tokens declared in different precedence declarations associate,
 the one declared later has the higher precedence and is grouped first.
 @end itemize
 
 the one declared later has the higher precedence and is grouped first.
 @end itemize
 

+For backward compatibility, there is a confusing difference between the
+argument lists of @code{%token} and precedence declarations.
+Only a @code{%token} can associate a literal string with a token type name.
+A precedence declaration always interprets a literal string as a reference to a
+separate token.
+For example:
+
+@example
+%left  OR "<="         // Does not declare an alias.
+%left  OR 134 "<=" 135 // Declares 134 for OR and 135 for "<=".
+@end example
+

 @node Union Decl
 @subsection The Collection of Value Types
 @cindex declaring value types
 @node Union Decl
 @subsection The Collection of Value Types
 @cindex declaring value types


@@ -4487,7 +4520,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 +4536,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.


@@ -4530,14 +4563,17 @@ valid grammar.
 @cindex push parser
 @findex %define api.push_pull
 
 @cindex push parser
 @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 
+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)
+
+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


@@ -4549,26 +4585,26 @@ parser (@pxref{Decl Summary,,%define api.push_pull}):
 
 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
 
 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 api.pure

 %define api.push_pull "push"
 @end example
 
 %define api.push_pull "push"
 @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 +4618,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 +4635,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 api.push_pull "push"} declaration with 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}
 @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 
+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
 @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
 generated parser by calling @code{yypull_parse}.
 This makes the @code{yyparse} function that is generated with the
 @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

-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,8 +4663,8 @@ 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 api.push_pull "both"} as it did for 
+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
 @code{%define api.push_pull "push"}.
 
 @node Decl Summary


@@ -4810,7 +4846,7 @@ already defined, so that the debugging facilities are compiled.
 Define a variable to adjust Bison's behavior.
 The possible choices for @var{variable}, as well as their meanings, depend on
 the selected target language and/or the parser skeleton (@pxref{Decl
 Define a variable to adjust Bison's behavior.
 The possible choices for @var{variable}, as well as their meanings, depend on
 the selected target language and/or the parser skeleton (@pxref{Decl

-Summary,,%language}).
+Summary,,%language}, @pxref{Decl Summary,,%skeleton}).

 
 Bison will warn if a @var{variable} is defined multiple times.
 
 
 Bison will warn if a @var{variable} is defined multiple times.
 


@@ -4837,6 +4873,20 @@ 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 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
 
 @item api.push_pull
 @findex %define api.push_pull
 


@@ -4845,6 +4895,8 @@ Some of the accepted @var{variable}s are:
 
 @item Purpose: Requests a pull parser, a push parser, or both.
 @xref{Push Decl, ,A Push Parser}.
 
 @item Purpose: Requests a pull parser, a push parser, or both.
 @xref{Push Decl, ,A Push Parser}.

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 
 @item Accepted Values: @code{"pull"}, @code{"push"}, @code{"both"}
 
 
 @item Accepted Values: @code{"pull"}, @code{"push"}, @code{"both"}
 


@@ -4873,8 +4925,9 @@ are useless in the generated parser.
 @item Caveats:
 
 @itemize @bullet
 @item Caveats:
 
 @itemize @bullet

-@item Unreachable states may contain conflicts and may reduce rules not
-reduced in any other state.
+
+@item Unreachable states may contain conflicts and may use rules not used in
+any other state.

 Thus, keeping unreachable states may induce warnings that are irrelevant to
 your parser's behavior, and it may eliminate warnings that are relevant.
 Of course, the change in warnings may actually be relevant to a parser table
 Thus, keeping unreachable states may induce warnings that are irrelevant to
 your parser's behavior, and it may eliminate warnings that are relevant.
 Of course, the change in warnings may actually be relevant to a parser table


@@ -5004,8 +5057,11 @@ chosen as if the input file were named @file{@var{prefix}.y}.
 
 @deffn {Directive} %language "@var{language}"
 Specify the programming language for the generated parser.  Currently
 
 @deffn {Directive} %language "@var{language}"
 Specify the programming language for the generated parser.  Currently

-supported languages include C and C++.
+supported languages include C, C++, and Java.

 @var{language} is case-insensitive.
 @var{language} is case-insensitive.

+
+This directive is experimental and its effect may be modified in future
+releases.

 @end deffn
 
 @deffn {Directive} %locations
 @end deffn
 
 @deffn {Directive} %locations


@@ -5022,10 +5078,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 +5110,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}"


@@ -5066,10 +5122,10 @@ Require a Version of Bison}.
 @deffn {Directive} %skeleton "@var{file}"
 Specify the skeleton to use.
 
 @deffn {Directive} %skeleton "@var{file}"
 Specify the skeleton to use.
 

-You probably don't need this option unless you are developing Bison.
-You should use @code{%language} if you want to specify the skeleton for a
-different language, because it is clearer and because it will always choose the
-correct skeleton for non-deterministic or push parsers.
+@c You probably don't need this option unless you are developing Bison.
+@c You should use @code{%language} if you want to specify the skeleton for a
+@c different language, because it is clearer and because it will always choose the
+@c correct skeleton for non-deterministic or push parsers.

 
 If @var{file} does not contain a @code{/}, @var{file} is the name of a skeleton
 file in the Bison installation directory.
 
 If @var{file} does not contain a @code{/}, @var{file} is the name of a skeleton
 file in the Bison installation directory.


@@ -5141,10 +5197,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 +5232,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 +5322,16 @@ 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 api.push_pull "push"} or 
-@code{%define api.push_pull "both"} declaration is used.  
+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)
+
+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 +5340,12 @@ 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 api.push_pull "both"} 
-declaration is used.  
+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)
+
+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,23 +5356,31 @@ 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 api.push_pull "push"} or 
-@code{%define api.push_pull "both"} declaration is used.  
+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)
+
+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)
 The fuction will return a valid parser instance if there was memory available
 @xref{Push Decl, ,A Push Parser}.
 
 @deftypefun yypstate *yypstate_new (void)
 The fuction will return a valid parser instance if there was memory available

-or NULL if no memory was available.
+or 0 if no memory was available.
+In impure mode, it will also return 0 if a parser instance is currently
+allocated.

 @end deftypefun
 
 @node Parser Delete Function
 @section The Parser Delete Function @code{yystate_delete}
 @findex yypstate_delete
 
 @end deftypefun
 
 @node Parser Delete Function
 @section The Parser Delete Function @code{yystate_delete}
 @findex yypstate_delete
 

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)
+

 You call the function @code{yypstate_delete} to delete a parser instance.
 You call the function @code{yypstate_delete} to delete a parser instance.

-function is available if either the @code{%define api.push_pull "push"} or 
-@code{%define api.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 +5568,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 +5619,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 +5627,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 +5693,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 +5711,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@}


@@ -6158,7 +6229,8 @@ shift and when to reduce.
 
 @menu
 * Why Precedence::    An example showing why precedence is needed.
 
 @menu
 * Why Precedence::    An example showing why precedence is needed.

-* Using Precedence::  How to specify precedence in Bison grammars.
+* Using Precedence::  How to specify precedence and associativity.
+* Precedence Only::   How to specify precedence only.

 * Precedence Examples::  How these features are used in the previous example.
 * How Precedence::    How they work.
 @end menu
 * Precedence Examples::  How these features are used in the previous example.
 * How Precedence::    How they work.
 @end menu


@@ -6213,8 +6285,9 @@ makes right-associativity.
 @node Using Precedence
 @subsection Specifying Operator Precedence
 @findex %left
 @node Using Precedence
 @subsection Specifying Operator Precedence
 @findex %left

-@findex %right

 @findex %nonassoc
 @findex %nonassoc

+@findex %precedence
+@findex %right

 
 Bison allows you to specify these choices with the operator precedence
 declarations @code{%left} and @code{%right}.  Each such declaration
 
 Bison allows you to specify these choices with the operator precedence
 declarations @code{%left} and @code{%right}.  Each such declaration


@@ -6224,13 +6297,63 @@ those operators left-associative and the @code{%right} declaration makes
 them right-associative.  A third alternative is @code{%nonassoc}, which
 declares that it is a syntax error to find the same operator twice ``in a
 row''.
 them right-associative.  A third alternative is @code{%nonassoc}, which
 declares that it is a syntax error to find the same operator twice ``in a
 row''.

+The last alternative, @code{%precedence}, allows to define only
+precedence and no associativity at all.  As a result, any
+associativity-related conflict that remains will be reported as an
+compile-time error.  The directive @code{%nonassoc} creates run-time
+error: using the operator in a associative way is a syntax error.  The
+directive @code{%precedence} creates compile-time errors: an operator
+@emph{can} be involved in an associativity-related conflict, contrary to
+what expected the grammar author.

 
 The relative precedence of different operators is controlled by the
 
 The relative precedence of different operators is controlled by the

-order in which they are declared.  The first @code{%left} or
-@code{%right} declaration in the file declares the operators whose
+order in which they are declared.  The first precedence/associativity
+declaration in the file declares the operators whose

 precedence is lowest, the next such declaration declares the operators
 whose precedence is a little higher, and so on.
 
 precedence is lowest, the next such declaration declares the operators
 whose precedence is a little higher, and so on.
 

+@node Precedence Only
+@subsection Specifying Precedence Only
+@findex %precedence
+
+Since @acronym{POSIX} Yacc defines only @code{%left}, @code{%right}, and
+@code{%nonassoc}, which all defines precedence and associativity, little
+attention is paid to the fact that precedence cannot be defined without
+defining associativity.  Yet, sometimes, when trying to solve a
+conflict, precedence suffices.  In such a case, using @code{%left},
+@code{%right}, or @code{%nonassoc} might hide future (associativity
+related) conflicts that would remain hidden.
+
+The dangling @code{else} ambiguity (@pxref{Shift/Reduce, , Shift/Reduce
+Conflicts}) can be solved explictly.  This shift/reduce conflicts occurs
+in the following situation, where the period denotes the current parsing
+state:
+
+@example
+if @var{e1} then if  @var{e2} then @var{s1} . else @var{s2}
+@end example
+
+The conflict involves the reduction of the rule @samp{IF expr THEN
+stmt}, which precedence is by default that of its last token
+(@code{THEN}), and the shifting of the token @code{ELSE}.  The usual
+disambiguation (attach the @code{else} to the closest @code{if}),
+shifting must be preferred, i.e., the precedence of @code{ELSE} must be
+higher than that of @code{THEN}.  But neither is expected to be involved
+in an associativity related conflict, which can be specified as follows.
+
+@example
+%precedence THEN
+%precedence ELSE
+@end example
+
+The unary-minus is another typical example where associativity is
+usually over-specified, see @ref{Infix Calc, , Infix Notation
+Calculator: @code{calc}}.  The @code{%left} directive is traditionaly
+used to declare the precedence of @code{NEG}, which is more than needed
+since it also defines its associativity.  While this is harmless in the
+traditional example, who knows how @code{NEG} might be used in future
+evolutions of the grammar@dots{}
+

 @node Precedence Examples
 @subsection Precedence Examples
 
 @node Precedence Examples
 @subsection Precedence Examples
 


@@ -6292,8 +6415,8 @@ outlandish at first, but it is really very common.  For example, a minus
 sign typically has a very high precedence as a unary operator, and a
 somewhat lower precedence (lower than multiplication) as a binary operator.
 
 sign typically has a very high precedence as a unary operator, and a
 somewhat lower precedence (lower than multiplication) as a binary operator.
 

-The Bison precedence declarations, @code{%left}, @code{%right} and
-@code{%nonassoc}, can only be used once for a given token; so a token has
+The Bison precedence declarations
+can only be used once for a given token; so a token has

 only one precedence declared in this way.  For context-dependent
 precedence, you need to use an additional mechanism: the @code{%prec}
 modifier for rules.
 only one precedence declared in this way.  For context-dependent
 precedence, you need to use an additional mechanism: the @code{%prec}
 modifier for rules.


@@ -7140,9 +7263,9 @@ useless: STR;
 @command{bison} reports:
 
 @example
 @command{bison} reports:
 
 @example

-calc.y: warning: 1 useless nonterminal and 1 useless rule
-calc.y:11.1-7: warning: useless nonterminal: useless
-calc.y:11.10-12: warning: useless rule: useless: STR
+calc.y: warning: 1 nonterminal and 1 rule useless in grammar
+calc.y:11.1-7: warning: nonterminal useless in grammar: useless
+calc.y:11.10-12: warning: rule useless in grammar: useless: STR

 calc.y: conflicts: 7 shift/reduce
 @end example
 
 calc.y: conflicts: 7 shift/reduce
 @end example
 


@@ -7181,17 +7304,17 @@ State 11 conflicts: 4 shift/reduce
 The next section reports useless tokens, nonterminal and rules.  Useless
 nonterminals and rules are removed in order to produce a smaller parser,
 but useless tokens are preserved, since they might be used by the
 The next section reports useless tokens, nonterminal and rules.  Useless
 nonterminals and rules are removed in order to produce a smaller parser,
 but useless tokens are preserved, since they might be used by the

-scanner (note the difference between ``useless'' and ``not used''
+scanner (note the difference between ``useless'' and ``unused''

 below):
 
 @example
 below):
 
 @example

-Useless nonterminals:
+Nonterminals useless in grammar:

    useless
 
    useless
 

-Terminals which are not used:
+Terminals unused in grammar:

    STR
 
    STR
 

-Useless rules:
+Rules useless in grammar:

 #6     useless: STR;
 @end example
 
 #6     useless: STR;
 @end example
 


@@ -7718,6 +7841,46 @@ traditional Yacc grammars.  If your grammar uses a Bison extension
 like @samp{%glr-parser}, Bison might not be Yacc-compatible even if
 this option is specified.
 
 like @samp{%glr-parser}, Bison might not be Yacc-compatible even if
 this option is specified.
 

+@item -W
+@itemx --warnings
+Output warnings falling in @var{category}.  @var{category} can be one
+of:
+@table @code
+@item midrule-values
+Warn about mid-rule values that are set but not used within any of the actions
+of the parent rule.
+For example, warn about unused @code{$2} in:
+
+@example
+exp: '1' @{ $$ = 1; @} '+' exp @{ $$ = $1 + $4; @};
+@end example
+
+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
+ exp: '1' @{ $1 = 1; @} '+' exp @{ $$ = $2 + $4; @};
+@end example
+
+These warnings are not enabled by default since they sometimes prove to
+be false alarms in existing grammars employing the Yacc constructs
+@code{$0} or @code{$-@var{n}} (where @var{n} is some positive integer).
+
+
+@item yacc
+Incompatibilities with @acronym{POSIX} Yacc.
+
+@item all
+All the warnings.
+@item none
+Turn off all the warnings.
+@item error
+Treat warnings as errors.
+@end table
+
+A category can be turned off by prefixing its name with @samp{no-}.  For
+instance, @option{-Wno-syntax} will hide the warnings about unused
+variables.

 @end table
 
 @noindent
 @end table
 
 @noindent


@@ -7730,13 +7893,21 @@ In the parser file, define the macro @code{YYDEBUG} to 1 if it is not
 already defined, so that the debugging facilities are compiled.
 @xref{Tracing, ,Tracing Your Parser}.
 
 already defined, so that the debugging facilities are compiled.
 @xref{Tracing, ,Tracing Your Parser}.
 

+@item -D @var{name}[=@var{value}]
+@itemx --define=@var{name}[=@var{value}]
+Same as running @samp{%define @var{name} "@var{value}"} (@pxref{Decl
+Summary, ,%define}).
+

 @item -L @var{language}
 @itemx --language=@var{language}
 Specify the programming language for the generated parser, as if
 @code{%language} was specified (@pxref{Decl Summary, , Bison Declaration
 @item -L @var{language}
 @itemx --language=@var{language}
 Specify the programming language for the generated parser, as if
 @code{%language} was specified (@pxref{Decl Summary, , Bison Declaration

-Summary}).  Currently supported languages include C and C++.
+Summary}).  Currently supported languages include C, C++, and Java.

 @var{language} is case-insensitive.
 
 @var{language} is case-insensitive.
 

+This option is experimental and its effect may be modified in future
+releases.
+

 @item --locations
 Pretend that @code{%locations} was specified.  @xref{Decl Summary}.
 
 @item --locations
 Pretend that @code{%locations} was specified.  @xref{Decl Summary}.
 


@@ -7758,10 +7929,10 @@ parser file, treating it as an independent source file in its own right.
 Specify the skeleton to use, similar to @code{%skeleton}
 (@pxref{Decl Summary, , Bison Declaration Summary}).
 
 Specify the skeleton to use, similar to @code{%skeleton}
 (@pxref{Decl Summary, , Bison Declaration Summary}).
 

-You probably don't need this option unless you are developing Bison.
-You should use @option{--language} if you want to specify the skeleton for a
-different language, because it is clearer and because it will always
-choose the correct skeleton for non-deterministic or push parsers.
+@c You probably don't need this option unless you are developing Bison.
+@c You should use @option{--language} if you want to specify the skeleton for a
+@c different language, because it is clearer and because it will always
+@c choose the correct skeleton for non-deterministic or push parsers.

 
 If @var{file} does not contain a @code{/}, @var{file} is the name of a skeleton
 file in the Bison installation directory.
 
 If @var{file} does not contain a @code{/}, @var{file} is the name of a skeleton
 file in the Bison installation directory.


@@ -7778,14 +7949,15 @@ Pretend that @code{%token-table} was specified.  @xref{Decl Summary}.
 Adjust the output:
 
 @table @option
 Adjust the output:
 
 @table @option

-@item -d
-@itemx --defines
+@item --defines[=@var{file}]

 Pretend that @code{%defines} was specified, i.e., write an extra output
 file containing macro definitions for the token type names defined in
 the grammar, as well as a few other declarations.  @xref{Decl Summary}.
 
 Pretend that @code{%defines} was specified, i.e., write an extra output
 file containing macro definitions for the token type names defined in
 the grammar, as well as a few other declarations.  @xref{Decl Summary}.
 

-@item --defines=@var{defines-file}
-Same as above, but save in the file @var{defines-file}.
+@item -d
+This is the same as @code{--defines} except @code{-d} does not accept a
+@var{file} argument since POSIX Yacc requires that @code{-d} can be bundled
+with other short options.

 
 @item -b @var{file-prefix}
 @itemx --file-prefix=@var{prefix}
 
 @item -b @var{file-prefix}
 @itemx --file-prefix=@var{prefix}


@@ -7811,6 +7983,9 @@ Implies @code{state} and augments the description of the automaton with
 the full set of items for each state, instead of its core only.
 @end table
 
 the full set of items for each state, instead of its core only.
 @end table
 

+@item --report-file=@var{file}
+Specify the @var{file} for the verbose description.
+

 @item -v
 @itemx --verbose
 Pretend that @code{%verbose} was specified, i.e., write an extra output
 @item -v
 @itemx --verbose
 Pretend that @code{%verbose} was specified, i.e., write an extra output


@@ -7824,17 +7999,23 @@ Specify the @var{file} for the parser file.
 The other output files' names are constructed from @var{file} as
 described under the @samp{-v} and @samp{-d} options.
 
 The other output files' names are constructed from @var{file} as
 described under the @samp{-v} and @samp{-d} options.
 

-@item -g
+@item -g[@var{file}]
+@itemx --graph[=@var{file}]

 Output a graphical representation of the @acronym{LALR}(1) grammar
 automaton computed by Bison, in @uref{http://www.graphviz.org/, Graphviz}
 @uref{http://www.graphviz.org/doc/info/lang.html, @acronym{DOT}} format.
 Output a graphical representation of the @acronym{LALR}(1) grammar
 automaton computed by Bison, in @uref{http://www.graphviz.org/, Graphviz}
 @uref{http://www.graphviz.org/doc/info/lang.html, @acronym{DOT}} format.

-If the grammar file is @file{foo.y}, the output file will
-be @file{foo.dot}.
-
-@item --graph=@var{graph-file}
-The behavior of @var{--graph} is the same than @samp{-g}.  The only
-difference is that it has an optional argument which is the name of
-the output graph file.
+@code{@var{file}} is optional.
+If omitted and the grammar file is @file{foo.y}, the output file will be
+@file{foo.dot}.
+
+@item -x[@var{file}]
+@itemx --xml[=@var{file}]
+Output an XML report of the @acronym{LALR}(1) automaton computed by Bison.
+@code{@var{file}} is optional.
+If omitted and the grammar file is @file{foo.y}, the output file will be
+@file{foo.xml}.
+(The current XML schema is experimental and may evolve.
+More user feedback will help to stabilize it.)

 @end table
 
 @node Option Cross Key
 @end table
 
 @node Option Cross Key


@@ -7846,20 +8027,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


@@ -7912,13 +8080,13 @@ int yyparse (void);
 
 @node C++ Bison Interface
 @subsection C++ Bison Interface
 
 @node C++ Bison Interface
 @subsection C++ Bison Interface

-@c - %language "C++"
+@c - %skeleton "lalr1.cc"

 @c - Always pure
 @c - initial action
 
 @c - Always pure
 @c - initial action
 

-The C++ @acronym{LALR}(1) parser is selected using the language directive,
-@samp{%language "C++"}, or the synonymous command-line option
-@option{--language=c++}.
+The C++ @acronym{LALR}(1) parser is selected using the skeleton directive,
+@samp{%skeleton "lalr1.c"}, or the synonymous command-line option
+@option{--skeleton=lalr1.c}.

 @xref{Decl Summary}.
 
 When run, @command{bison} will create several entities in the @samp{yy}
 @xref{Decl Summary}.
 
 When run, @command{bison} will create several entities in the @samp{yy}


@@ -8108,7 +8276,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


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

-%language "C++"                          /*  -*- 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"


@@ -8452,6 +8620,7 @@ exp: exp '+' exp   @{ $$ = $1 + $3; @}
    | exp '-' exp   @{ $$ = $1 - $3; @}
    | exp '*' exp   @{ $$ = $1 * $3; @}
    | exp '/' exp   @{ $$ = $1 / $3; @}
    | exp '-' exp   @{ $$ = $1 - $3; @}
    | exp '*' exp   @{ $$ = $1 * $3; @}
    | exp '/' exp   @{ $$ = $1 / $3; @}

+   | '(' exp ')'   @{ $$ = $2; @}

    | "identifier"  @{ $$ = driver.variables[*$1]; delete $1; @}
    | "number"      @{ $$ = $1; @};
 %%
    | "identifier"  @{ $$ = driver.variables[*$1]; delete $1; @}
    | "number"      @{ $$ = $1; @};
 %%


@@ -8556,7 +8725,7 @@ It is convenient to use a typedef to shorten
   typedef yy::calcxx_parser::token token;
 %@}
            /* Convert ints to the actual type of tokens.  */
   typedef yy::calcxx_parser::token token;
 %@}
            /* Convert ints to the actual type of tokens.  */

-[-+*/]     return yy::calcxx_parser::token_type (yytext[0]);
+[-+*/()]   return yy::calcxx_parser::token_type (yytext[0]);

 ":="       return token::ASSIGN;
 @{int@}      @{
   errno = 0;
 ":="       return token::ASSIGN;
 @{int@}      @{
   errno = 0;


@@ -8610,6 +8779,7 @@ The top level file, @file{calc++.cc}, poses no problem.
 int
 main (int argc, char *argv[])
 @{
 int
 main (int argc, char *argv[])
 @{

+  int res = 0;

   calcxx_driver driver;
   for (++argv; argv[0]; ++argv)
     if (*argv == std::string ("-p"))
   calcxx_driver driver;
   for (++argv; argv[0]; ++argv)
     if (*argv == std::string ("-p"))


@@ -8618,6 +8788,9 @@ main (int argc, char *argv[])
       driver.trace_scanning = true;
     else if (!driver.parse (*argv))
       std::cout << driver.result << std::endl;
       driver.trace_scanning = true;
     else if (!driver.parse (*argv))
       std::cout << driver.result << std::endl;

+    else
+      res = 1;
+  return res;

 @}
 @end example
 
 @}
 @end example
 


@@ -8629,46 +8802,64 @@ main (int argc, char *argv[])
 * Java Semantic Values::         %type and %token vs. Java
 * Java Location Values::         The position and location classes
 * Java Parser Interface::        Instantiating and running the parser
 * Java Semantic Values::         %type and %token vs. Java
 * Java Location Values::         The position and location classes
 * Java Parser Interface::        Instantiating and running the parser

-* Java Scanner Interface::       Java scanners, and pure parsers
+* Java Scanner Interface::       Specifying the scanner for the parser
+* Java Action Features::         Special features for use in actions.

 * Java Differences::             Differences between C/C++ and Java Grammars
 * Java Differences::             Differences between C/C++ and Java Grammars

+* Java Declarations Summary::    List of Bison declarations used with Java

 @end menu
 
 @node Java Bison Interface
 @subsection Java Bison Interface
 @c - %language "Java"
 @end menu
 
 @node Java Bison Interface
 @subsection Java Bison Interface
 @c - %language "Java"

-@c - initial action

 
 

-The Java parser skeletons are selected using a language directive,
-@samp{%language "Java"}, or the synonymous command-line option
-@option{--language=java}.
+(The current Java interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 
 

-When run, @command{bison} will create several entities whose name
-starts with @samp{YY}.  Use the @samp{%name-prefix} directive to
-change the prefix, see @ref{Decl Summary}; classes can be placed
-in an arbitrary Java package using a @samp{%define package} section.
+The Java parser skeletons are selected using the @code{%language "Java"}
+directive or the @option{-L java}/@option{--language=java} option.

 
 

-The parser class defines an inner class, @code{Location}, that is used
-for location tracking.  If the parser is pure, it also defines an
-inner interface, @code{Lexer}; see~@ref{Java Scanner Interface} for the
-meaning of pure parsers when the Java language is chosen.  Other than
-these inner class/interface, and the members described in~@ref{Java
-Parser Interface}, all the other members and fields are preceded
-with a @code{yy} prefix to avoid clashes with user code.
-
-No header file can be generated for Java parsers; you must not pass
-@option{-d}/@option{--defines} to @command{bison}, nor use the
-@samp{%defines} directive.
+@c FIXME: Documented bug.
+When generating a Java parser, @code{bison @var{basename}.y} will create
+a single Java source file named @file{@var{basename}.java}.  Using an
+input file without a @file{.y} suffix is currently broken.  The basename
+of the output file can be changed by the @code{%file-prefix} directive
+or the @option{-p}/@option{--name-prefix} option.  The entire output file
+name can be changed by the @code{%output} directive or the
+@option{-o}/@option{--output} option.  The output file contains a single
+class for the parser.

 
 

-By default, the @samp{YYParser} class has package visibility.  A
-declaration @samp{%define "public"} will change to public visibility.
-Remember that, according to the Java language specification, the name
-of the @file{.java} file should match the name of the class in this
-case.
+You can create documentation for generated parsers using Javadoc.
+
+Contrary to C parsers, Java parsers do not use global variables; the
+state of the parser is always local to an instance of the parser class.
+Therefore, all Java parsers are ``pure'', and the @code{%pure-parser}
+and @code{%define api.pure} directives does not do anything when used in
+Java.

 
 

-Similarly, a declaration @samp{%define "abstract"} will make your
-class abstract.
+Push parsers are currently unsupported in Java and @code{%define
+api.push_pull} have no effect.
+
+@acronym{GLR} parsers are currently unsupported in Java.  Do not use the
+@code{glr-parser} directive.
+
+No header file can be generated for Java parsers.  Do not use the
+@code{%defines} directive or the @option{-d}/@option{--defines} options.
+
+@c FIXME: Possible code change.
+Currently, support for debugging is always compiled
+in.  Thus the @code{%debug} and @code{%token-table} directives and the
+@option{-t}/@option{--debug} and @option{-k}/@option{--token-table}
+options have no effect.  This may change in the future to eliminate
+unused code in the generated parser, so use @code{%debug} explicitly
+if needed.  Also, in the future the
+@code{%token-table} directive might enable a public interface to
+access the token names and codes.
+
+Getting a ``code too large'' error from the Java compiler means the code
+hit the 64KB bytecode per method limination of the Java class file.
+Try reducing the amount of code in actions and static initializers;
+otherwise, report a bug so that the parser skeleton will be improved.

 
 

-You can create documentation for generated parsers using Javadoc.

 
 @node Java Semantic Values
 @subsection Java Semantic Values
 
 @node Java Semantic Values
 @subsection Java Semantic Values


@@ -8688,20 +8879,23 @@ semantic values' types (class names) should be specified in the
 By default, the semantic stack is declared to have @code{Object} members,
 which means that the class types you specify can be of any class.
 To improve the type safety of the parser, you can declare the common
 By default, the semantic stack is declared to have @code{Object} members,
 which means that the class types you specify can be of any class.
 To improve the type safety of the parser, you can declare the common

-superclass of all the semantic values using the @samp{%define} directive.
-For example, after the following declaration:
+superclass of all the semantic values using the @code{%define stype}
+directive.  For example, after the following declaration:

 
 @example
 
 @example

-%define "stype" "ASTNode"
+%define stype "ASTNode"

 @end example
 
 @noindent
 any @code{%type} or @code{%token} specifying a semantic type which
 is not a subclass of ASTNode, will cause a compile-time error.
 
 @end example
 
 @noindent
 any @code{%type} or @code{%token} specifying a semantic type which
 is not a subclass of ASTNode, will cause a compile-time error.
 

+@c FIXME: Documented bug.

 Types used in the directives may be qualified with a package name.
 Primitive data types are accepted for Java version 1.5 or later.  Note
 that in this case the autoboxing feature of Java 1.5 will be used.
 Types used in the directives may be qualified with a package name.
 Primitive data types are accepted for Java version 1.5 or later.  Note
 that in this case the autoboxing feature of Java 1.5 will be used.

+Generic types may not be used; this is due to a limitation in the
+implementation of Bison, and may change in future releases.

 
 Java parsers do not support @code{%destructor}, since the language
 adopts garbage collection.  The parser will try to hold references
 
 Java parsers do not support @code{%destructor}, since the language
 adopts garbage collection.  The parser will try to hold references


@@ -8724,20 +8918,29 @@ An auxiliary user-defined class defines a @dfn{position}, a single point
 in a file; Bison itself defines a class representing a @dfn{location},
 a range composed of a pair of positions (possibly spanning several
 files).  The location class is an inner class of the parser; the name
 in a file; Bison itself defines a class representing a @dfn{location},
 a range composed of a pair of positions (possibly spanning several
 files).  The location class is an inner class of the parser; the name

-is @code{Location} by default, may also be renamed using @code{%define
-"location_type" "@var{class-name}}.
+is @code{Location} by default, and may also be renamed using
+@code{%define location_type "@var{class-name}}.

 
 The location class treats the position as a completely opaque value.
 By default, the class name is @code{Position}, but this can be changed
 
 The location class treats the position as a completely opaque value.
 By default, the class name is @code{Position}, but this can be changed

-with @code{%define "position_type" "@var{class-name}"}.
+with @code{%define position_type "@var{class-name}"}.  This class must
+be supplied by the user.

 
 
 
 

-@deftypemethod {Location} {Position} begin
-@deftypemethodx {Location} {Position} end
+@deftypeivar {Location} {Position} begin
+@deftypeivarx {Location} {Position} end

 The first, inclusive, position of the range, and the first beyond.
 The first, inclusive, position of the range, and the first beyond.

-@end deftypemethod
+@end deftypeivar

 
 

-@deftypemethod {Location} {void} toString ()
+@deftypeop {Constructor} {Location} {} Location (Position @var{loc})
+Create a @code{Location} denoting an empty range located at a given point. 
+@end deftypeop
+
+@deftypeop {Constructor} {Location} {} Location (Position @var{begin}, Position @var{end})
+Create a @code{Location} from the endpoints of the range.
+@end deftypeop
+
+@deftypemethod {Location} {String} toString ()

 Prints the range represented by the location.  For this to work
 properly, the position class should override the @code{equals} and
 @code{toString} methods appropriately.
 Prints the range represented by the location.  For this to work
 properly, the position class should override the @code{equals} and
 @code{toString} methods appropriately.


@@ -8752,28 +8955,85 @@ properly, the position class should override the @code{equals} and
 @c   debug_stream.
 @c - Reporting errors
 
 @c   debug_stream.
 @c - Reporting errors
 

-The output file defines the parser class in the package optionally
-indicated in the @code{%define package} section.  The class name defaults
-to @code{YYParser}.  The @code{YY} prefix may be changed using
-@samp{%name-prefix}; alternatively, you can use @samp{%define
-"parser_class_name" "@var{name}"} to give a custom name to the class.
-The interface of this class is detailed below.  It can be extended using
-the @code{%parse-param} directive; each occurrence of the directive will
-add a field to the parser class, and an argument to its constructor.
+The name of the generated parser class defaults to @code{YYParser}.  The
+@code{YY} prefix may be changed using the @code{%name-prefix} directive
+or the @option{-p}/@option{--name-prefix} option.  Alternatively, use
+@code{%define parser_class_name "@var{name}"} to give a custom name to
+the class.  The interface of this class is detailed below.
+
+By default, the parser class has package visibility.  A declaration
+@code{%define public} will change to public visibility.  Remember that,
+according to the Java language specification, the name of the @file{.java}
+file should match the name of the class in this case.  Similarly, you can
+use @code{abstract}, @code{final} and @code{strictfp} with the
+@code{%define} declaration to add other modifiers to the parser class.
+A single @code{%define annotations "@var{annotations}"} directive can
+be used to add any number of annotations to the parser class.
+
+The Java package name of the parser class can be specified using the
+@code{%define package} directive.  The superclass and the implemented
+interfaces of the parser class can be specified with the @code{%define
+extends} and @code{%define implements} directives.

 
 

-@deftypemethod {YYParser} {} YYParser (@var{type1} @var{arg1}, ...)
-Build a new parser object.  There are no arguments by default, unless
-@samp{%parse-param @{@var{type1} @var{arg1}@}} was used.
-@end deftypemethod
+The parser class defines an inner class, @code{Location}, that is used
+for location tracking (see @ref{Java Location Values}), and a inner
+interface, @code{Lexer} (see @ref{Java Scanner Interface}).  Other than
+these inner class/interface, and the members described in the interface
+below, all the other members and fields are preceded with a @code{yy} or
+@code{YY} prefix to avoid clashes with user code.
+
+The parser class can be extended using the @code{%parse-param}
+directive. Each occurrence of the directive will add a @code{protected
+final} field to the parser class, and an argument to its constructor,
+which initialize them automatically.
+
+@deftypeop {Constructor} {YYParser} {} YYParser (@var{lex_param}, @dots{}, @var{parse_param}, @dots{})
+Build a new parser object with embedded @code{%code lexer}.  There are
+no parameters, unless @code{%parse-param}s and/or @code{%lex-param}s are
+used.
+
+Use @code{%code init} for code added to the start of the constructor
+body. This is especially useful to initialize superclasses. Use
+@code{%define init_throws} to specify any uncatch exceptions.
+@end deftypeop
+
+@deftypeop {Constructor} {YYParser} {} YYParser (Lexer @var{lexer}, @var{parse_param}, @dots{})
+Build a new parser object using the specified scanner.  There are no
+additional parameters unless @code{%parse-param}s are used.
+
+If the scanner is defined by @code{%code lexer}, this constructor is
+declared @code{protected} and is called automatically with a scanner
+created with the correct @code{%lex-param}s.
+
+Use @code{%code init} for code added to the start of the constructor
+body. This is especially useful to initialize superclasses. Use
+@code{%define init_throws} to specify any uncatch exceptions.
+@end deftypeop

 
 @deftypemethod {YYParser} {boolean} parse ()
 Run the syntactic analysis, and return @code{true} on success,
 @code{false} otherwise.
 @end deftypemethod
 
 
 @deftypemethod {YYParser} {boolean} parse ()
 Run the syntactic analysis, and return @code{true} on success,
 @code{false} otherwise.
 @end deftypemethod
 

+@deftypemethod {YYParser} {boolean} getErrorVerbose ()
+@deftypemethodx {YYParser} {void} setErrorVerbose (boolean @var{verbose})
+Get or set the option to produce verbose error messages.  These are only
+available with the @code{%error-verbose} directive, which also turn on
+verbose error messages.
+@end deftypemethod
+
+@deftypemethod {YYParser} {void} yyerror (String @var{msg})
+@deftypemethodx {YYParser} {void} yyerror (Position @var{pos}, String @var{msg})
+@deftypemethodx {YYParser} {void} yyerror (Location @var{loc}, String @var{msg})
+Print an error message using the @code{yyerror} method of the scanner
+instance in use. The @code{Location} and @code{Position} parameters are
+available only if location tracking is active.
+@end deftypemethod
+

 @deftypemethod {YYParser} {boolean} recovering ()
 During the syntactic analysis, return @code{true} if recovering
 @deftypemethod {YYParser} {boolean} recovering ()
 During the syntactic analysis, return @code{true} if recovering

-from a syntax error.  @xref{Error Recovery}.
+from a syntax error.
+@xref{Error Recovery}.

 @end deftypemethod
 
 @deftypemethod {YYParser} {java.io.PrintStream} getDebugStream ()
 @end deftypemethod
 
 @deftypemethod {YYParser} {java.io.PrintStream} getDebugStream ()


@@ -8788,12 +9048,10 @@ Get or set the tracing level.  Currently its value is either 0, no trace,
 or nonzero, full tracing.
 @end deftypemethod
 
 or nonzero, full tracing.
 @end deftypemethod
 

-@deftypemethod {YYParser} {void} error (Location @var{l}, String @var{m})
-The definition for this member function must be supplied by the user
-in the same way as the scanner interface (@pxref{Java Scanner
-Interface}); the parser uses it to report a parser error occurring at
-@var{l}, described by @var{m}.
-@end deftypemethod
+@deftypecv {Constant} {YYParser} {String} {bisonVersion}
+@deftypecvx {Constant} {YYParser} {String} {bisonSkeleton}
+Identify the Bison version and skeleton used to generate this parser.
+@end deftypecv

 
 
 @node Java Scanner Interface
 
 
 @node Java Scanner Interface


@@ -8802,24 +9060,20 @@ Interface}); the parser uses it to report a parser error occurring at
 @c - %lex-param
 @c - Lexer interface
 
 @c - %lex-param
 @c - Lexer interface
 

-Contrary to C parsers, Java parsers do not use global variables; the
-state of the parser is always local to an instance of the parser class.
-Therefore, all Java parsers are ``pure'', and the @code{%pure-parser}
-directive does not do anything when used in Java.
-
-The scanner always resides in a separate class than the parser.
-Still, Java also two possible ways to interface a Bison-generated Java
-parser with a scanner, that is, the scanner may reside in a separate file
-than the Bison grammar, or in the same file.  The interface
-to the scanner is similar in the two cases.
+There are two possible ways to interface a Bison-generated Java parser
+with a scanner: the scanner may be defined by @code{%code lexer}, or
+defined elsewhere.  In either case, the scanner has to implement the
+@code{Lexer} inner interface of the parser class.  This interface also
+contain constants for all user-defined token names and the predefined
+@code{EOF} token.

 
 

-In the first case, where the scanner in the same file as the grammar, the
-scanner code has to be placed in @code{%code lexer} blocks.  If you want
-to pass parameters from the parser constructor to the scanner constructor,
-specify them with @code{%lex-param}; they are passed before
-@code{%parse-param}s to the constructor.
+In the first case, the body of the scanner class is placed in
+@code{%code lexer} blocks.  If you want to pass parameters from the
+parser constructor to the scanner constructor, specify them with
+@code{%lex-param}; they are passed before @code{%parse-param}s to the
+constructor.

 
 

-In the second case, the scanner has to implement interface @code{Lexer},
+In the second case, the scanner has to implement the @code{Lexer} interface,

 which is defined within the parser class (e.g., @code{YYParser.Lexer}).
 The constructor of the parser object will then accept an object
 implementing the interface; @code{%lex-param} is not used in this
 which is defined within the parser class (e.g., @code{YYParser.Lexer}).
 The constructor of the parser object will then accept an object
 implementing the interface; @code{%lex-param} is not used in this


@@ -8827,18 +9081,19 @@ case.
 
 In both cases, the scanner has to implement the following methods.
 
 
 In both cases, the scanner has to implement the following methods.
 

-@deftypemethod {Lexer} {void} yyerror (Location @var{l}, String @var{m})
-As explained in @pxref{Java Parser Interface}, this method is defined
-by the user to emit an error message.  The first parameter is omitted
-if location tracking is not active.  Its type can be changed using
-@samp{%define "location_type" "@var{class-name}".}
+@deftypemethod {Lexer} {void} yyerror (Location @var{loc}, String @var{msg})
+This method is defined by the user to emit an error message.  The first
+parameter is omitted if location tracking is not active.  Its type can be
+changed using @code{%define location_type "@var{class-name}".}

 @end deftypemethod
 
 @end deftypemethod
 

-@deftypemethod {Lexer} {int} yylex (@var{type1} @var{arg1}, ...)
+@deftypemethod {Lexer} {int} yylex ()

 Return the next token.  Its type is the return value, its semantic
 value and location are saved and returned by the ther methods in the
 Return the next token.  Its type is the return value, its semantic
 value and location are saved and returned by the ther methods in the

-interface.  Invocations of @samp{%lex-param @{@var{type1}
-@var{arg1}@}} yield additional arguments.
+interface.
+
+Use @code{%define lex_throws} to specify any uncaught exceptions.
+Default is @code{java.io.IOException}.

 @end deftypemethod
 
 @deftypemethod {Lexer} {Position} getStartPos ()
 @end deftypemethod
 
 @deftypemethod {Lexer} {Position} getStartPos ()


@@ -8847,55 +9102,101 @@ Return respectively the first position of the last token that
 @code{yylex} returned, and the first position beyond it.  These
 methods are not needed unless location tracking is active.
 
 @code{yylex} returned, and the first position beyond it.  These
 methods are not needed unless location tracking is active.
 

-The return type can be changed using @samp{%define "position_type"
+The return type can be changed using @code{%define position_type

 "@var{class-name}".}
 @end deftypemethod
 
 @deftypemethod {Lexer} {Object} getLVal ()
 "@var{class-name}".}
 @end deftypemethod
 
 @deftypemethod {Lexer} {Object} getLVal ()

-Return respectively the first position of the last token that yylex
-returned, and the first position beyond it.
+Return the semantical value of the last token that yylex returned.

 
 

-The return type can be changed using @samp{%define "stype"
+The return type can be changed using @code{%define stype

 "@var{class-name}".}
 @end deftypemethod
 
 
 "@var{class-name}".}
 @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.
+@node Java Action Features
+@subsection Special Features for Use in Java Actions

 
 

-@deftypemethod {YYParser} {void} error (Location @var{l}, String @var{m})
-As explained in @pxref{Java Parser Interface}, this method is defined
-by the user to emit an error message.  The first parameter is not used
-unless location tracking is active.  Its type can be changed using
-@samp{%define "location_type" "@var{class-name}".}
-@end deftypemethod
+The following special constructs can be uses in Java actions.
+Other analogous C action features are currently unavailable for Java.

 
 

-@deftypemethod {YYParser} {int} yylex (@var{type1} @var{arg1}, ...)
-Return the next token.  Its type is the return value, its semantic
-value and location are saved into @code{yylval}, @code{yystartpos},
-@code{yyendpos}.  Invocations of @samp{%lex-param @{@var{type1}
-@var{arg1}@}} yield additional arguments.
-@end deftypemethod
+Use @code{%define throws} to specify any uncaught exceptions from parser
+actions, and initial actions specified by @code{%initial-action}.

 
 

-@deftypecv {Field} {YYParser} Position yystartpos
-@deftypecvx {Field} {YYParser} Position yyendpos
-Contain respectively the first position of the last token that yylex
-returned, and the first position beyond it.  These methods are not
-needed unless location tracking is active.
+@defvar $@var{n}
+The semantic value for the @var{n}th component of the current rule.
+This may not be assigned to.
+@xref{Java Semantic Values}.
+@end defvar

 
 

-The field's type can be changed using @samp{%define "position_type"
-"@var{class-name}".}
-@end deftypecv
+@defvar $<@var{typealt}>@var{n}
+Like @code{$@var{n}} but specifies a alternative type @var{typealt}.
+@xref{Java Semantic Values}.
+@end defvar

 
 

-@deftypecv {Field} {YYParser} Object yylval
-Return respectively the first position of the last token that yylex
-returned, and the first position beyond it.
+@defvar $$
+The semantic value for the grouping made by the current rule.  As a
+value, this is in the base type (@code{Object} or as specified by
+@code{%define stype}) as in not cast to the declared subtype because
+casts are not allowed on the left-hand side of Java assignments.
+Use an explicit Java cast if the correct subtype is needed.
+@xref{Java Semantic Values}.
+@end defvar
+
+@defvar $<@var{typealt}>$
+Same as @code{$$} since Java always allow assigning to the base type.
+Perhaps we should use this and @code{$<>$} for the value and @code{$$}
+for setting the value but there is currently no easy way to distinguish
+these constructs.
+@xref{Java Semantic Values}.
+@end defvar
+
+@defvar @@@var{n}
+The location information of the @var{n}th component of the current rule.
+This may not be assigned to.
+@xref{Java Location Values}.
+@end defvar
+
+@defvar @@$
+The location information of the grouping made by the current rule.
+@xref{Java Location Values}.
+@end defvar
+
+@deffn {Statement} {return YYABORT;}
+Return immediately from the parser, indicating failure.
+@xref{Java Parser Interface}.
+@end deffn
+
+@deffn {Statement} {return YYACCEPT;}
+Return immediately from the parser, indicating success.
+@xref{Java Parser Interface}.
+@end deffn
+
+@deffn {Statement} {return YYERROR;}
+Start error recovery without printing an error message. 
+@xref{Error Recovery}.
+@end deffn
+
+@deffn {Statement} {return YYFAIL;}
+Print an error message and start error recovery. 
+@xref{Error Recovery}.
+@end deffn
+
+@deftypefn {Function} {boolean} recovering ()
+Return whether error recovery is being done. In this state, the parser
+reads token until it reaches a known state, and then restarts normal
+operation.
+@xref{Error Recovery}.
+@end deftypefn
+
+@deftypefn  {Function} {void} yyerror (String @var{msg})
+@deftypefnx {Function} {void} yyerror (Position @var{loc}, String @var{msg})
+@deftypefnx {Function} {void} yyerror (Location @var{loc}, String @var{msg})
+Print an error message using the @code{yyerror} method of the scanner
+instance in use. The @code{Location} and @code{Position} parameters are
+available only if location tracking is active.
+@end deftypefn

 
 

-The field's type can be changed using @samp{%define "stype"
-"@var{class-name}".}
-@end deftypecv

 
 @node Java Differences
 @subsection Differences between C/C++ and Java Grammars
 
 @node Java Differences
 @subsection Differences between C/C++ and Java Grammars


@@ -8912,6 +9213,7 @@ macros.  Instead, they should be preceded by @code{return} when they
 appear in an action.  The actual definition of these symbols is
 opaque to the Bison grammar, and it might change in the future.  The
 only meaningful operation that you can do, is to return them.
 appear in an action.  The actual definition of these symbols is
 opaque to the Bison grammar, and it might change in the future.  The
 only meaningful operation that you can do, is to return them.

+See @pxref{Java Action Features}.

 
 Note that of these three symbols, only @code{YYACCEPT} and
 @code{YYABORT} will cause a return from the @code{yyparse}
 
 Note that of these three symbols, only @code{YYACCEPT} and
 @code{YYABORT} will cause a return from the @code{yyparse}


@@ -8919,6 +9221,17 @@ method@footnote{Java parsers include the actions in a separate
 method than @code{yyparse} in order to have an intuitive syntax that
 corresponds to these C macros.}.
 
 method than @code{yyparse} in order to have an intuitive syntax that
 corresponds to these C macros.}.
 

+@item
+Java lacks unions, so @code{%union} has no effect.  Instead, semantic
+values have a common base type: @code{Object} or as specified by
+@code{%define stype}.  Angle backets on @code{%token}, @code{type},
+@code{$@var{n}} and @code{$$} specify subtypes rather than fields of
+an union.  The type of @code{$$}, even with angle brackets, is the base
+type since Java casts are not allow on the left-hand side of assignments.
+Also, @code{$@var{n}} and @code{@@@var{n}} are not allowed on the
+left-hand side of assignments. See @pxref{Java Semantic Values} and
+@pxref{Java Action Features}.
+

 @item
 The prolog declarations have a different meaning than in C/C++ code.
 @table @asis
 @item
 The prolog declarations have a different meaning than in C/C++ code.
 @table @asis


@@ -8938,10 +9251,170 @@ Interface}).
 @end table
 
 Other @code{%code} blocks are not supported in Java parsers.
 @end table
 
 Other @code{%code} blocks are not supported in Java parsers.

+In particular, @code{%@{ @dots{} %@}} blocks should not be used
+and may give an error in future versions of Bison.
+

 The epilogue has the same meaning as in C/C++ code and it can
 The epilogue has the same meaning as in C/C++ code and it can

-be used to define other classes used by the parser.
+be used to define other classes used by the parser @emph{outside}
+the parser class.

 @end itemize
 
 @end itemize
 

+
+@node Java Declarations Summary
+@subsection Java Declarations Summary
+
+This summary only include declarations specific to Java or have special
+meaning when used in a Java parser.
+
+@deffn {Directive} {%language "Java"}
+Generate a Java class for the parser.
+@end deffn
+
+@deffn {Directive} %lex-param @{@var{type} @var{name}@}
+A parameter for the lexer class defined by @code{%code lexer}
+@emph{only}, added as parameters to the lexer constructor and the parser
+constructor that @emph{creates} a lexer.  Default is none.
+@xref{Java Scanner Interface}.
+@end deffn
+
+@deffn {Directive} %name-prefix "@var{prefix}"
+The prefix of the parser class name @code{@var{prefix}Parser} if
+@code{%define parser_class_name} is not used.  Default is @code{YY}.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} %parse-param @{@var{type} @var{name}@}
+A parameter for the parser class added as parameters to constructor(s)
+and as fields initialized by the constructor(s).  Default is none.
+@xref{Java Parser Interface}.
+@end deffn
+
+@deffn {Directive} %token <@var{type}> @var{token} @dots{}
+Declare tokens.  Note that the angle brackets enclose a Java @emph{type}.
+@xref{Java Semantic Values}.
+@end deffn
+
+@deffn {Directive} %type <@var{type}> @var{nonterminal} @dots{}
+Declare the type of nonterminals.  Note that the angle brackets enclose
+a Java @emph{type}.
+@xref{Java Semantic Values}.
+@end deffn
+
+@deffn {Directive} %code @{ @var{code} @dots{} @}
+Code appended to the inside of the parser class.
+@xref{Java Differences}.
+@end deffn
+
+@deffn {Directive} {%code imports} @{ @var{code} @dots{} @}
+Code inserted just after the @code{package} declaration.
+@xref{Java Differences}.
+@end deffn
+
+@deffn {Directive} {%code init} @{ @var{code} @dots{} @}
+Code inserted at the beginning of the parser constructor body.
+@xref{Java Parser Interface}.
+@end deffn
+
+@deffn {Directive} {%code lexer} @{ @var{code} @dots{} @}
+Code added to the body of a inner lexer class within the parser class.
+@xref{Java Scanner Interface}.
+@end deffn
+
+@deffn {Directive} %% @var{code} @dots{}
+Code (after the second @code{%%}) appended to the end of the file,
+@emph{outside} the parser class.
+@xref{Java Differences}.
+@end deffn
+
+@deffn {Directive} %@{ @var{code} @dots{} %@}
+Not supported.  Use @code{%code imports} instead.
+@xref{Java Differences}.
+@end deffn
+
+@deffn {Directive} {%define abstract}
+Whether the parser class is declared @code{abstract}.  Default is false.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define annotations} "@var{annotations}"
+The Java annotations for the parser class.  Default is none.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define extends} "@var{superclass}"
+The superclass of the parser class.  Default is none.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define final}
+Whether the parser class is declared @code{final}.  Default is false.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define implements} "@var{interfaces}"
+The implemented interfaces of the parser class, a comma-separated list.
+Default is none.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define init_throws} "@var{exceptions}"
+The exceptions thrown by @code{%code init} from the parser class
+constructor.  Default is none.
+@xref{Java Parser Interface}.
+@end deffn
+
+@deffn {Directive} {%define lex_throws} "@var{exceptions}"
+The exceptions thrown by the @code{yylex} method of the lexer, a
+comma-separated list.  Default is @code{java.io.IOException}.
+@xref{Java Scanner Interface}.
+@end deffn
+
+@deffn {Directive} {%define location_type} "@var{class}"
+The name of the class used for locations (a range between two
+positions).  This class is generated as an inner class of the parser
+class by @command{bison}.  Default is @code{Location}.
+@xref{Java Location Values}.
+@end deffn
+
+@deffn {Directive} {%define package} "@var{package}"
+The package to put the parser class in.  Default is none.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define parser_class_name} "@var{name}"
+The name of the parser class.  Default is @code{YYParser} or
+@code{@var{name-prefix}Parser}.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define position_type} "@var{class}"
+The name of the class used for positions. This class must be supplied by
+the user.  Default is @code{Position}.
+@xref{Java Location Values}.
+@end deffn
+
+@deffn {Directive} {%define public}
+Whether the parser class is declared @code{public}.  Default is false.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define stype} "@var{class}"
+The base type of semantic values.  Default is @code{Object}.
+@xref{Java Semantic Values}.
+@end deffn
+
+@deffn {Directive} {%define strictfp}
+Whether the parser class is declared @code{strictfp}.  Default is false.
+@xref{Java Bison Interface}.
+@end deffn
+
+@deffn {Directive} {%define throws} "@var{exceptions}"
+The exceptions thrown by user-supplied parser actions and
+@code{%initial-action}, a comma-separated list.  Default is none.
+@xref{Java Parser Interface}.
+@end deffn
+
+

 @c ================================================= FAQ
 
 @node FAQ
 @c ================================================= FAQ
 
 @node FAQ


@@ -8996,7 +9469,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


@@ -9502,7 +9975,7 @@ Specify the programming language for the generated parser.
 @end deffn
 
 @deffn {Directive} %left
 @end deffn
 
 @deffn {Directive} %left

-Bison declaration to assign left associativity to token(s).
+Bison declaration to assign precedence and left associativity to token(s).

 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 
 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 


@@ -9537,7 +10010,7 @@ parser file.  @xref{Decl Summary}.
 @end deffn
 
 @deffn {Directive} %nonassoc
 @end deffn
 
 @deffn {Directive} %nonassoc

-Bison declaration to assign nonassociativity to token(s).
+Bison declaration to assign precedence and nonassociativity to token(s).

 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 
 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 


@@ -9557,9 +10030,14 @@ Bison declaration to assign a precedence to a specific rule.
 @xref{Contextual Precedence, ,Context-Dependent Precedence}.
 @end deffn
 
 @xref{Contextual Precedence, ,Context-Dependent Precedence}.
 @end deffn
 

+@deffn {Directive} %precedence
+Bison declaration to assign precedence to token(s), but no associativity
+@xref{Precedence Decl, ,Operator Precedence}.
+@end deffn
+

 @deffn {Directive} %pure-parser
 @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}"


@@ -9568,7 +10046,7 @@ Require a Version of Bison}.
 @end deffn
 
 @deffn {Directive} %right
 @end deffn
 
 @deffn {Directive} %right

-Bison declaration to assign right associativity to token(s).
+Bison declaration to assign precedence and right associativity to token(s).

 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 
 @xref{Precedence Decl, ,Operator Precedence}.
 @end deffn
 


@@ -9736,7 +10214,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,30 +10225,38 @@ 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}}.
 @code{yypstate_delete}}.

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 @end deffn
 
 @deffn {Function} yypstate_new
 @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}}.
 @code{yypstate_new}}.

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 @end deffn
 
 @deffn {Function} yypull_parse
 @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}}.
 @code{yypull_parse}}.

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 @end deffn
 
 @deffn {Function} yypush_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}}.
 @code{yypush_parse}}.

+(The current push parsing interface is experimental and may evolve.
+More user feedback will help to stabilize it.)

 @end deffn
 
 @deffn {Macro} YYPARSE_PARAM
 @end deffn
 
 @deffn {Macro} YYPARSE_PARAM