summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMarc Autret <autret_m@epita.fr>2001-11-26 19:19:21 +0000
committerMarc Autret <autret_m@epita.fr>2001-11-26 19:19:21 +0000
commitc18cf8cb264f2751fa34ba05491d3c20e30516d8 (patch)
tree7383c3af3f5c71ede0a4d9255666c2c0d32b574d /doc
parent54b982ae70d0469feca06d41a236203a7bea218d (diff)
downloadbison-c18cf8cb264f2751fa34ba05491d3c20e30516d8.tar.gz
Revert doc patch.
Diffstat (limited to 'doc')
-rw-r--r--doc/bison.texinfo5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 1abf856e..5449086f 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -4506,9 +4506,8 @@ produce parsers that are very large. In practice, Bison is more useful
as it is now.
When the problem arises, you can often fix it by identifying the two
-parser states that are being confused (using @samp{-v}
-(@pxref{Invocation, ,Invoking Bison}) can help), and adding something to
-make them look distinct. In the above example, adding one rule to
+parser states that are being confused, and adding something to make them
+look distinct. In the above example, adding one rule to
@code{return_spec} as follows makes the problem go away:
@example