bison-patches
[Top][All Lists]
Advanced

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

[PATCH] Comment changes.


From: Akim Demaille
Subject: [PATCH] Comment changes.
Date: Thu, 19 Feb 2009 21:16:21 -0000

        * data/glr.cc: here.
---
 ChangeLog   |    5 +++++
 data/glr.cc |    4 ++--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index a3d1da5..9abe7d4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,10 @@
 2009-02-19  Akim Demaille  <address@hidden>
 
+       Comment changes.
+       * data/glr.cc: here.
+
+2009-02-19  Akim Demaille  <address@hidden>
+
        Remove trailing blanks.
        The epilogue has its own ending 
        , no need to add another.
diff --git a/data/glr.cc b/data/glr.cc
index fa1dfd3..8463bb7 100644
--- a/data/glr.cc
+++ b/data/glr.cc
@@ -27,7 +27,7 @@
 #
 #   The additional arguments are stored as members of the parser
 #   object, yyparser.  The C routines need to carry yyparser
-#   throughout the C parser; that easy: just let yyparser become an
+#   throughout the C parser; that's easy: make yyparser an
 #   additional parse-param.  But because the C++ skeleton needs to
 #   know the "real" original parse-param, we save them
 #   (b4_parse_param_orig).  Note that b4_parse_param is overquoted
@@ -37,7 +37,7 @@
 # The locations
 #
 #   We use location.cc just like lalr1.cc, but because glr.c stores
-#   the locations in a (C++) union, the position and location classes
+#   the locations in a union, the position and location classes
 #   must not have a constructor.  Therefore, contrary to lalr1.cc, we
 #   must not define "b4_location_constructors".  As a consequence the
 #   user must initialize the first positions (in particular the
-- 
1.6.2.rc0.35.g1b53





reply via email to

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