Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-07-23 11:10:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

* doc/bison.texinfo (Mystery Conflicts): Hint '-v' use.

Browse Source 
From Golubev I. N.
This commit is contained in:
Marc Autret
2001-11-25 13:02:55 +00:00
parent c64a20f3dc
commit b83f0407c6
3 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ChangeLog
+5
View File
@@ -1,3 +1,8 @@
2001-11-25 Marc Autret <[email protected]>
* doc/bison.texinfo (Mystery Conflicts): Hint '-v' use.
From Golubev I. N.
2001-11-23 Akim Demaille <[email protected]>
* lib/alloca.c: Update, from fileutils.
THANKS
+1
View File
@@ -9,6 +9,7 @@ Daniel Hagerty [email protected]
David J. MacKenzie [email protected]
Dick Streefland [email protected]
Fabrice Bauzac [email protected]
Golubev I. N [email protected]
Hans Aberg [email protected]
Jesse Thilo [email protected]
Jim Meyering [email protected]
doc/bison.texinfo
+3 -2
View File
@@ -4507,8 +4507,9 @@ 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, and adding something to make them
look distinct. In the above example, adding one rule to
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
@code{return_spec} as follows makes the problem go away:
@example