[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: look-ahead -> lookahead

From: Paul Eggert
Subject: Re: look-ahead -> lookahead
Date: Sun, 11 Jun 2006 01:17:15 -0700
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)

Thanks.  I installed the following minor fixups for that.

2006-06-11  Paul Eggert  <address@hidden>

        * NEWS: Reword the post-2.3 change to not be so optimistic about
        removing the old "look-ahead" spelling.
        Update previous look-ahead/lookahead change reports.
        * REFERENCES: look-ahead -> lookahead (since that's
        what he actually wrote).
        * doc/refcard.tex: look ahead -> lookahead,
        look-ahead -> lookahead

Index: NEWS
RCS file: /cvsroot/bison/bison/NEWS,v
retrieving revision 1.149
diff -p -u -r1.149 NEWS
--- NEWS        10 Jun 2006 03:02:22 -0000      1.149
+++ NEWS        11 Jun 2006 08:13:16 -0000
@@ -4,7 +4,8 @@ Bison News
 Changes in version 2.3+:
 * The option `--report=look-ahead' has been changed to `--report=lookahead'.
-  The old spelling still works but is not documented and will be removed.
+  The old spelling still works, but is not documented and may be removed
+  in a future release.
 Changes in version 2.3, 2006-06-05:
@@ -164,8 +165,7 @@ Changes in version 2.0, 2004-12-25:
     This is a GNU extension.
   - The option `--report=lookahead' was changed to `--report=look-ahead'.
-    The old spelling still works, but is not documented and will be
-    removed.
+    [However, this was changed back after 2.3.]
   - Experimental %destructor support has been added to
@@ -432,8 +432,8 @@ Changes in version 1.50, 2002-10-04:
   produces additional information:
   - itemset
     complete the core item sets with their closure
-  - lookahead [changed to `look-ahead' in 1.875e and later]
-    explicitly associate look-ahead tokens to items
+  - lookahead [changed to `look-ahead' in 1.875e through 2.3, but changed back]
+    explicitly associate lookahead tokens to items
   - solved
     describe shift/reduce conflicts solving.
     Bison used to systematically output this information on top of
RCS file: /cvsroot/bison/bison/REFERENCES,v
retrieving revision 1.2
diff -p -u -r1.2 REFERENCES
--- REFERENCES  21 Jun 2004 20:20:30 -0000      1.2
+++ REFERENCES  11 Jun 2006 08:13:16 -0000
@@ -19,7 +19,7 @@ kludges that Johnson had to perpetrate t
 Also, Bison uses a faster but less space-efficient encoding for the
 parse tables (see Corbett's PhD thesis from Berkeley, "Static
 Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
-85/251), and more modern technique for generating the look-ahead sets.
+85/251), and more modern technique for generating the lookahead sets.
 (See Frank DeRemer and Thomas Pennello, "Efficient Computation of
 LALR(1) Look-Ahead Sets", ACM Transactions on Programming Languages
 and Systems (TOPLAS) 4, 4 (October 1982), 615-649.  Their
Index: doc/refcard.tex
RCS file: /cvsroot/bison/bison/doc/refcard.tex,v
retrieving revision 1.3
diff -p -u -r1.3 refcard.tex
--- doc/refcard.tex     14 May 2005 06:49:46 -0000      1.3
+++ doc/refcard.tex     11 Jun 2006 08:13:16 -0000
@@ -458,7 +458,7 @@ as either {\tt first_column} or {\tt las
 \section {Variables and Types}
-\key{Current look ahead token.}                {yychar}
+\key{Current lookahead token.}                 {yychar}
 \key{Debug mode flag.}                         {yydebug}
 \key{Data associated with the current token.}  {yylval}
 \key{Source position of current token.}        {yylloc}
@@ -489,8 +489,8 @@ as either {\tt first_column} or {\tt las
 \key{Quit parsing immediately. Return 1.}           {YYABORT}
 \key{Quit parsing immediately. Return 0.}           {YYACCEPT}
 \key{Pretend a syntax error occurred.}              {YYERROR}
-\key{Value in {\tt yychar} if no look-ahead token.} {YYEMPTY}
-\key{Clear previous look ahead token.}              {yyclearin}
+\key{Value in {\tt yychar} if no lookahead token.}  {YYEMPTY}
+\key{Clear previous lookahead token.}               {yyclearin}
 \key{Recover normally from an error.}               {yyerrok}
 % **************

reply via email to

[Prev in Thread] Current Thread [Next in Thread]