summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAkim Demaille <akim.demaille@gmail.com>2021-12-18 17:52:01 +0100
committerAkim Demaille <akim.demaille@gmail.com>2021-12-19 16:41:05 +0100
commitf8e8f57e9fa53b46cce53a9a8ddb9a346620282f (patch)
tree872918d8b5763ee0575b15ac9c3b9e82174f5dc2
parent6571c2d1b134bd04d81f1426c08985407e8c7087 (diff)
downloadbison-f8e8f57e9fa53b46cce53a9a8ddb9a346620282f.tar.gz
doc: add indexes
* doc/bison.texi (Special Tokens): here.
-rw-r--r--doc/bison.texi3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bison.texi b/doc/bison.texi
index 77357813..2dab6c49 100644
--- a/doc/bison.texi
+++ b/doc/bison.texi
@@ -7546,15 +7546,18 @@ utility can be used without change as the definition of @code{yylex}.
In addition to the user defined tokens, Bison generates a few special tokens
that @code{yylex} may return.
+@findex YYEOF
The @code{YYEOF} token denotes the end of file, and signals to the parser
that there is nothing left afterwards. @xref{Calling Convention}, for an
example.
+@findex YYUNDEF
Returning @code{YYUNDEF} tells the parser that some lexical error was found.
It will emit an error message about an ``invalid token'', and enter
error-recovery (@pxref{Error Recovery}). Returning an unknown token kind
results in the exact same behavior.
+@findex YYerror
Returning @code{YYerror} requires the parser to enter error-recovery
@emph{without} emitting an error message. This way the lexical analyzer can
produce an accurate error messages about the invalid input (something the