From: Akim Demaille Date: Thu, 26 Aug 2004 13:05:41 +0000 (+0000) Subject: * doc/bison.texinfo (Implementing Loops): Rename as... X-Git-Tag: BISON-2_0~123 X-Git-Url: https://git.saurik.com/bison.git/commitdiff_plain/2fa09258b1e86ece8ec50836be4a76e383b89cb4?ds=inline * doc/bison.texinfo (Implementing Loops): Rename as... (Implementing Gotos/Loops): this. --- diff --git a/ChangeLog b/ChangeLog index 5d3dfedc..f4adc707 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2004-08-26 Akim Demaille + + * doc/bison.texinfo (Implementing Loops): Rename as... + (Implementing Gotos/Loops): this. + 2004-08-13 Paul Eggert Adjust to latest gnulib. @@ -26,7 +31,7 @@ Fix bug with non-%union parsers that have printers or destructors, which led to a Bison core dump. Reported by Peter Fales in . - + * data/c.m4 (b4_symbol_actions): Don't assume %union was used. * data/lalr1.cc (yystype) [defined YYSTYPE]: Define to YYSTYPE, not to our own type. @@ -46,7 +51,7 @@ GLR writeups. E.g., avoid frenchspacing and the future tense, change "lookahead" to "look-ahead", and change "wrt" to "with respect to". - + 2004-06-21 Paul Hilfinger * doc/bison.texinfo (Merging GLR Parses, Compiler Requirements): @@ -126,7 +131,7 @@ (AM_GNU_GETTEXT_VERSION): Increase from 0.11.5 to 0.12. Add comments explaining why those particular versions are currently needed. - + * src/parse-gram.y (lloc_default): Rewrite to avoid compiler bug in SGI MIPSpro 7.4.1m. Problem reported by Albert Chin-A-Young in . diff --git a/doc/bison.texinfo b/doc/bison.texinfo index 41d13a7a..af459f2b 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -297,7 +297,7 @@ Frequently Asked Questions * How Can I Reset the Parser:: @code{yyparse} Keeps some State * Strings are Destroyed:: @code{yylval} Loses Track of Strings * C++ Parsers:: Compiling Parsers with C++ Compilers -* Implementing Loops:: Control Flow in the Calculator +* Implementing Gotos/Loops:: Control Flow in the Calculator Copying This Manual @@ -6683,7 +6683,7 @@ are addressed. * How Can I Reset the Parser:: @code{yyparse} Keeps some State * Strings are Destroyed:: @code{yylval} Loses Track of Strings * C++ Parsers:: Compiling Parsers with C++ Compilers -* Implementing Loops:: Control Flow in the Calculator +* Implementing Gotos/Loops:: Control Flow in the Calculator @end menu @node Parser Stack Overflow @@ -6869,12 +6869,12 @@ some simple C++ rules in mind, such as not including ``real classes'' pointer type to the root of your lexical/syntactic hierarchy. -@node Implementing Loops -@section Implementing Loops +@node Implementing Gotos/Loops +@section Implementing Gotos/Loops @display My simple calculator supports variables, assignments, and functions, -but how can I implement loops? +but how can I implement gotos, or loops? @end display Although very pedagogical, the examples included in the document blur