Comment changes.

	* data/glr.cc: here.

diff --git a/ChangeLog b/ChangeLog
index a3d1da56406b81a8b0f0c0f599c75041b68027e2..9abe7d44dc63db489ec3ae114f346ad629cbfbca 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2009-02-19  Akim Demaille  <demaille@gostai.com>
+
+       Comment changes.
+       * data/glr.cc: here.
+
 2009-02-19  Akim Demaille  <demaille@gostai.com>
 
        Remove trailing blanks.

diff --git a/data/glr.cc b/data/glr.cc
index fa1dfd366c10da2ce9616fcdbd841860a851e6da..8463bb7ad7859208955e14205d0e09bf6a6a320f 100644 (file)
--- 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