[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 01/11] doc: correct typo: s/can not/cannot/
From: |
Jim Meyering |
Subject: |
[PATCH 01/11] doc: correct typo: s/can not/cannot/ |
Date: |
Wed, 18 Jan 2012 11:30:47 +0100 |
From: Jim Meyering <address@hidden>
* doc/bison.texinfo (Bug Reports): s/can not/cannot/
And remove trailing blanks.
---
ChangeLog | 6 ++++++
doc/bison.texinfo | 18 +++++++++---------
2 files changed, 15 insertions(+), 9 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index faa7e18..1df15cd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2012-01-15 Jim Meyering <address@hidden>
+
+ doc: correct typo: s/can not/cannot/
+ * doc/bison.texinfo (Bug Reports): s/can not/cannot/
+ And remove trailing blanks.
+
2012-01-15 Akim Demaille <address@hidden>
java: fix reduction traces.
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 3bb41ab..b6604f6 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -1178,8 +1178,8 @@ Another Bison feature requiring special consideration is
@code{YYERROR}
initiate error recovery.
During deterministic GLR operation, the effect of @code{YYERROR} is
the same as its effect in a deterministic parser.
-The effect in a deferred action is similar, but the precise point of the
-error is undefined; instead, the parser reverts to deterministic operation,
+The effect in a deferred action is similar, but the precise point of the
+error is undefined; instead, the parser reverts to deterministic operation,
selecting an unspecified stack on which to continue with a syntax error.
In a semantic predicate (see @ref{Semantic Predicates}) during nondeterministic
parsing, @code{YYERROR} silently prunes
@@ -1210,12 +1210,12 @@ widget :
@end smallexample
@noindent
-is one way to allow the same parser to handle two different syntaxes for
+is one way to allow the same parser to handle two different syntaxes for
widgets. The clause preceded by @code{%?} is treated like an ordinary
action, except that its text is treated as an expression and is always
-evaluated immediately (even when in nondeterministic mode). If the
+evaluated immediately (even when in nondeterministic mode). If the
expression yields 0 (false), the clause is treated as a syntax error,
-which, in a nondeterministic parser, causes the stack in which it is reduced
+which, in a nondeterministic parser, causes the stack in which it is reduced
to die. In a deterministic parser, it acts like YYERROR.
As the example shows, predicates otherwise look like semantic actions, and
@@ -1226,7 +1226,7 @@ labels.
There is a subtle difference between semantic predicates and ordinary
actions in nondeterministic mode, since the latter are deferred.
-For example, we could try to rewrite the previous example as
+For example, we could try to rewrite the previous example as
@smallexample
widget :
@@ -1240,7 +1240,7 @@ widget :
false). However, this
does @emph{not} have the same effect if @code{new_args} and @code{old_args}
have overlapping syntax.
-Since the mid-rule actions testing @code{new_syntax} are deferred,
+Since the mid-rule actions testing @code{new_syntax} are deferred,
a GLR parser first encounters the unresolved ambiguous reduction
for cases where @code{new_args} and @code{old_args} recognize the same string
@emph{before} performing the tests of @code{new_syntax}. It therefore
@@ -7745,7 +7745,7 @@ that allows variable-length arrays. The default is 200.
Do not allow @code{YYINITDEPTH} to be greater than @code{YYMAXDEPTH}.
You can generate a deterministic parser containing C++ user code from
-the default (C) skeleton, as well as from the C++ skeleton
+the default (C) skeleton, as well as from the C++ skeleton
(@pxref{C++ Parsers}). However, if you do use the default skeleton
and want to allow the parsing stack to grow,
be careful not to use semantic types or location types that require
@@ -10937,7 +10937,7 @@ transcript of the build session, starting with the
invocation of
send additional files as well (such as `config.h' or `config.cache').
Patches are most welcome, but not required. That is, do not hesitate to
-send a bug report just because you can not provide a fix.
+send a bug report just because you cannot provide a fix.
Send bug reports to @email{bug-bison@@gnu.org}.
--
1.7.9.rc1.2.gccfe4
- [PATCH 04/11] maint: placate the space-TAB syntax-check, (continued)
- [PATCH 04/11] maint: placate the space-TAB syntax-check, Jim Meyering, 2012/01/18
- [PATCH 07/11] maint: include <config.h> first, Jim Meyering, 2012/01/18
- [PATCH 11/11] change more quotes in source, and adjust tests to match, Jim Meyering, 2012/01/18
- [PATCH 01/11] doc: correct typo: s/can not/cannot/,
Jim Meyering <=
- [PATCH 08/11] build: manually update bootstrap from gnulib, and adapt, Jim Meyering, 2012/01/18