[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bison.texinfo patch to avoid node name problem
From: |
Paul Eggert |
Subject: |
bison.texinfo patch to avoid node name problem |
Date: |
16 Jun 2003 22:22:08 -0700 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
texinfo format does not allow arbitrary '@' in node names, so I
installed this patch. Without this patch, Texinfo 4.6 couldn't build
the TeX version of the manual.
Index: bison.texinfo
===================================================================
RCS file: /cvsroot/bison/bison/doc/bison.texinfo,v
retrieving revision 1.108
retrieving revision 1.109
diff -p -u -r1.108 -r1.109
--- bison.texinfo 12 May 2003 19:34:21 -0000 1.108
+++ bison.texinfo 17 Jun 2003 05:15:49 -0000 1.109
@@ -284,7 +284,7 @@ Invoking Bison
Frequently Asked Questions
* Parser Stack Overflow:: Breaking the Stack Limits
-* How Can I Reset @code{yyparse}:: @code{yyparse} Keeps some State
+* 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
@@ -6356,7 +6356,7 @@ are addressed.
@menu
* Parser Stack Overflow:: Breaking the Stack Limits
-* How Can I Reset @code{yyparse}:: @code{yyparse} Keeps some State
+* 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
@@ -6373,8 +6373,8 @@ message. What can I do?
This question is already addressed elsewhere, @xref{Recursion,
,Recursive Rules}.
address@hidden How Can I Reset @code{yyparse}
address@hidden How Can I Reset @code{yyparse}
address@hidden How Can I Reset the Parser
address@hidden How Can I Reset the Parser
The following phenomenon has several symptoms, resulting in the
following typical questions:
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bison.texinfo patch to avoid node name problem,
Paul Eggert <=