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

Revert doc patch.

Browse Source
This commit is contained in:
Marc Autret
2001-11-26 19:13:40 +00:00
parent 2ca209c11d
commit a220f55509
3 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@@ -34,11 +34,6 @@
conflicts as expected.
* tests/regression.at (%expect right): Adjust.
2001-11-25 Marc Autret <autret_m@epita.fr>
* doc/bison.texinfo (Mystery Conflicts): Hint '-v' use.
From Golubev I. N.
2001-11-23 Akim Demaille <akim@epita.fr>
* lib/alloca.c: Update, from fileutils.

1
THANKS
View File

@@ -9,7 +9,6 @@ Daniel Hagerty hag@gnu.org
David J. MacKenzie djm@gnu.org
Dick Streefland dick.streefland@altium.nl
Fabrice Bauzac noon@cote-dazur.com
Golubev I. N gin@mo.msk.ru
Hans Aberg haberg@matematik.su.se
Jesse Thilo jthilo@gnu.org
Jim Meyering meyering@gnu.org

5
doc/bison.texinfo
View File

@@ -4507,9 +4507,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