mirror of
https://git.savannah.gnu.org/git/bison.git
synced 2026-03-14 23:03:04 +00:00
doc: fix lalr1.cc documentation.
* doc/bison.texinfo (C++ Scanner Interface): Fix yylex signature.
(C++ Bison Interface): Fix lalr1.cc skeleton name.
(C++ Parser Interface): Fix semantic_type and location_type names.
Document yy::parser::token.
Reported by Jerry Quinn.
(cherry picked from commit 0100cd629d)
Conflicts:
doc/bison.texinfo
This commit is contained in:
@@ -8329,8 +8329,8 @@ int yyparse (void);
|
||||
@c - initial action
|
||||
|
||||
The C++ deterministic parser is selected using the skeleton directive,
|
||||
@samp{%skeleton "lalr1.c"}, or the synonymous command-line option
|
||||
@option{--skeleton=lalr1.c}.
|
||||
@samp{%skeleton "lalr1.cc"}, or the synonymous command-line option
|
||||
@option{--skeleton=lalr1.cc}.
|
||||
@xref{Decl Summary}.
|
||||
|
||||
When run, @command{bison} will create several entities in the @samp{yy}
|
||||
@@ -8479,11 +8479,19 @@ this class is detailed below. It can be extended using the
|
||||
it describes an additional member of the parser class, and an
|
||||
additional argument for its constructor.
|
||||
|
||||
@defcv {Type} {parser} {semantic_value_type}
|
||||
@defcvx {Type} {parser} {location_value_type}
|
||||
@defcv {Type} {parser} {semantic_type}
|
||||
@defcvx {Type} {parser} {location_type}
|
||||
The types for semantics value and locations.
|
||||
@end defcv
|
||||
|
||||
@defcv {Type} {parser} {token}
|
||||
A structure that contains (only) the definition of the tokens as the
|
||||
@code{yytokentype} enumeration. To refer to the token @code{FOO}, the
|
||||
scanner should use @code{yy::parser::token::FOO}. The scanner can use
|
||||
@samp{typedef yy::parser::token token;} to ``import'' the token enumeration
|
||||
(@pxref{Calc++ Scanner}).
|
||||
@end defcv
|
||||
|
||||
@deftypemethod {parser} {} parser (@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.
|
||||
@@ -8522,7 +8530,7 @@ 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{%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}, ...)
|
||||
@deftypemethod {parser} {int} yylex (semantic_type* @var{yylval}, location_type* @var{yylloc}, @var{type1} @var{arg1}, ...)
|
||||
Return the next token. Its type is the return value, its semantic
|
||||
value and location being @var{yylval} and @var{yylloc}. Invocations of
|
||||
@samp{%lex-param @{@var{type1} @var{arg1}@}} yield additional arguments.
|
||||
|
||||
Reference in New Issue
Block a user