Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-15 07:13:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix documentation problems reported by Tim Josling at

Browse Source 
<http://lists.gnu.org/archive/html/bug-bison/2008-01/msg00013.html>.
* NEWS (2.3a+): Mention removal of --no-parser, -n, and %no-parser.
* doc/bison.texinfo (Token Decl): Token numbers are *nonnegative*
integers.  Explain the effect of literal string aliases on error
messages.  Copy token 0 documentation from the C++ skeleton
documentation.
This commit is contained in:
Joel E. Denny
2008-02-17 02:47:53 +00:00
parent ab7f29f8f9
commit b1cc23c4e3
3 changed files with 25 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
doc/bison.texinfo
View File

@@ -4023,7 +4023,7 @@ 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
@@ -4076,6 +4076,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}).
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