Fix documentation problems reported by Tim Josling at

<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.

diff --git a/ChangeLog b/ChangeLog
index bb9daa62b30b6c7bbca455f795d9447a15d83522..2d823f761b767ded36585cd3dc04a83d5aa8555d 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2008-02-16  Joel E. Denny  <jdenny@ces.clemson.edu>
+
+       Fix documentation problems reported by Tim Josling at
+       <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.
+

 2008-02-16  Joel E. Denny  <jdenny@ces.clemson.edu>
 
        Accept a token number in a %left, %right, or %nonassoc for POSIX
 2008-02-16  Joel E. Denny  <jdenny@ces.clemson.edu>
 
        Accept a token number in a %left, %right, or %nonassoc for POSIX

diff --git a/NEWS b/NEWS
index d0fc7abbc508891cce21f667c654ca73d123ac0c..1458cb2d3e06cf57bfca7276afedee34f2eebcbd 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -69,7 +69,7 @@ Changes in version 2.3a+ (????-??-??):
   for further discussion.
 
 * Lookahead Set Correction in the `.output' Report
   for further discussion.
 
 * Lookahead Set Correction in the `.output' Report

-  
+

   When instructed to generate a `.output' file including lookahead sets
   (using `--report=lookahead', for example), Bison now prints each reduction's
   lookahead set only next to the associated state's one item that (1) is
   When instructed to generate a `.output' file including lookahead sets
   (using `--report=lookahead', for example), Bison now prints each reduction's
   lookahead set only next to the associated state's one item that (1) is


@@ -158,6 +158,9 @@ Changes in version 2.3a+ (????-??-??):
   by POSIX.  However, see the end of section `Operator Precedence' in the Bison
   manual for a caveat concerning the treatment of literal strings.
 
   by POSIX.  However, see the end of section `Operator Precedence' in the Bison
   manual for a caveat concerning the treatment of literal strings.
 

+* The nonfunctional --no-parser, -n, and %no-parser options have been
+  completely removed from Bison.
+

 Changes in version 2.3a, 2006-09-13:
 
 * Instead of %union, you can define and use your own union type
 Changes in version 2.3a, 2006-09-13:
 
 * Instead of %union, you can define and use your own union type

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 72d027ac57b7be15e6fc3154d843633c454ee93f..bb6d5dcc4f9fd2ad546cd75a69cf88f3e48dae20 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -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
 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


@@ -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}).
 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