bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnu.org #222254] Bison Manual / typo report


From: Paul Eggert
Subject: Re: [gnu.org #222254] Bison Manual / typo report
Date: Wed, 23 Feb 2005 01:19:01 -0800
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux)

Thanks for reporting thse typos.  I have installed the following patch
to the Bison manual sources, and the fix should propagate to the
GNU/FSF web site after the next release.

2005-02-23  Paul Eggert  <address@hidden>

        * doc/bison.texinfo (Language and Grammar): some -> same
        (Epilogue): int he -> in the
        Typos reported by Sebastian Piping via Justin Pence.

Index: bison.texinfo
===================================================================
RCS file: /cvsroot/bison/bison/doc/bison.texinfo,v
retrieving revision 1.139
retrieving revision 1.140
diff -p -u -r1.139 -r1.140
--- bison.texinfo       24 Jan 2005 23:26:17 -0000      1.139
+++ bison.texinfo       23 Feb 2005 09:15:09 -0000      1.140
@@ -444,7 +444,7 @@ roughly that the next grammar rule to ap
 uniquely determined by the preceding input and a fixed, finite portion
 (called a @dfn{look-ahead}) of the remaining input.  A context-free
 grammar can be @dfn{ambiguous}, meaning that there are multiple ways to
-apply the grammar rules to get the some inputs.  Even unambiguous
+apply the grammar rules to get the same inputs.  Even unambiguous
 grammars can be @dfn{non-deterministic}, meaning that no fixed
 look-ahead always suffices to determine the next grammar rule to apply.
 With the proper declarations, Bison is also able to parse these more
@@ -2627,7 +2627,7 @@ not come before the definition of @code{
 definitions of @code{yylex} and @code{yyerror} often go here.  Because
 C requires functions to be declared before being used, you often need
 to declare functions like @code{yylex} and @code{yyerror} in the Prologue,
-even if you define them int he Epilogue.
+even if you define them in the Epilogue.
 @xref{Interface, ,Parser C-Language Interface}.
 
 If the last section is empty, you may omit the @samp{%%} that separates it




reply via email to

[Prev in Thread] Current Thread [Next in Thread]