Undo most of the 2002-11-12 yychar -> yytoken patch, as it broke GCC 3.2.1.

diff --git a/ChangeLog b/ChangeLog
index 1a192887aec09073ec7b4dfc66892da8b5a0cda4..c3698f8ad347c817c8e9f30ebb1ab64e0cf19bf6 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,19 @@
+2002-12-15  Paul Eggert  <eggert@twinsun.com>
+
+       Undo most of the 2002-11-12 yychar -> yytoken patch, as it broke
+       GCC 3.2.1 (which depends on yychar == YYEMPTY when there is no
+       lookahead symbol, and which sets yychar in parser actions) and it
+       disagreed with the Bison documentation.  This should fix the bug
+       reported by Andrew Walrond in
+       <http://mail.gnu.org/pipermail/bug-bison/2002-December/001949.html>.
+       
+       * data/yacc.c (YYTRANSLATE): Don't check for negative argument,
+       as the caller now does that.
+       (yyclearin, YYBACKUP, yyparse): Use yychar, not yytoken.
+       (YYEMPTY): Parenthesize right hand side, since others use it.
+       (yyparse): Don't assume that our generated code is the only code
+       that sets yychar.
+
 2002-12-13  Paul Eggert  <eggert@twinsun.com>
 
        Version 1.75d.
@@ -6,7 +22,7 @@
        * src/Makefile.am (bin_SCRIPTS): New macro, for yacc.
        (MOSTLYCLEANFILES): Add yacc.
        (yacc): New rule.
-       * docbison.texinfo (Invocation, Bison Options): Mention yacc
+       * doc/bison.texinfo (Invocation, Bison Options): Mention yacc
        as an alias for bison y.
 
        * po/LINGUAS: Add da.