* doc/bison.texinfo: here.
Reported by Alex Rozenman.
---
ChangeLog | 6 ++++++
doc/bison.texinfo | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 504b0f5..2811304 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2009-09-17 Akim Demaille <[email protected]>
+
+ doc: fixes.
+ * doc/bison.texinfo: here.
+ Reported by Alex Rozenman.
+
2009-09-16 Akim Demaille <[email protected]>
doc: lalr1.cc and variants.
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index e38bfa5..8f40afb 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -8617,7 +8617,7 @@ alias analysis must be disabled}. Use the option
There might be portability issues we are not aware of.
@end itemize
-As far as we know, these limitations \emph{can} be alleviated. All it takes
+As far as we know, these limitations @emph{can} be alleviated. All it takes
is some time and/or some talented C++ hacker willing to contribute to Bison.
@node C++ Location Values
@@ -9113,7 +9113,7 @@ definition of ``symbol'', we enable @code{lex_symbol}.
@findex %code requires
Then come the declarations/inclusions needed by the semantic values.
Because the parser uses the parsing driver and reciprocally, both would like
-to include the header of the other, which is, of course, insane. These
+to include the header of the other, which is, of course, insane. This
mutual dependency will be broken using forward declarations. Because the
driver's header needs detailed knowledge about the parser class (in
particular its inner types), it is the parser's header which will use a
--
1.6.4.3
