autoconf-patches
[Top][All Lists]
Advanced

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

Re: autoupdate fun


From: Ralf Wildenhues
Subject: Re: autoupdate fun
Date: Wed, 22 Mar 2006 20:30:55 +0100
User-agent: Mutt/1.5.9i

* Ralf Wildenhues wrote on Mon, Mar 20, 2006 at 09:33:50PM CET:
> A couple of issues with autoupdate

Stepan's patch forced me to actually read autoupdate.in.  I found some
typos in the (well-written!) documentation "how autoupdate functions".

I have applied the patch below to fix them, in the hope that that was ok
to do.

Cheers,
Ralf

        * bin/autoupdate.in: Fix some typos.

Index: bin/autoupdate.in
===================================================================
RCS file: /cvsroot/autoconf/autoconf/bin/autoupdate.in,v
retrieving revision 1.57
diff -u -r1.57 autoupdate.in
--- bin/autoupdate.in   14 Feb 2006 23:18:51 -0000      1.57
+++ bin/autoupdate.in   22 Mar 2006 12:29:53 -0000
@@ -419,7 +416,7 @@
 # The task of `autoupdate' is not trivial: the biggest difficulty being
 # that you must limit the changes to the parts that really need to be
 # updated.  Finding a satisfying implementation proved to be quite hard,
-# as this is the fourth implementation of `autoupdate'.
+# as this is the fifth implementation of `autoupdate'.
 #
 # Below, we will use a simple example of obsolete macro:
 #
@@ -602,7 +599,7 @@
 # strings which can become quickly huge, which slows it significantly.
 #
 # In particular one should avoid as much as possible to use `define' for
-# temporaries.  Now that `define' as quite a complex meaning, it is an
+# temporaries.  Now that `define' has quite a complex meaning, it is an
 # expensive operations that should be limited to macros.  Use
 # `m4_define' for temporaries.
 #
@@ -717,7 +714,7 @@
 # No big deal for the semantics (unless the macro depends upon $#, which
 # is bad), but the users would not be happy.
 #
-# Additionally, we introduced quotes that we not there before, which is
+# Additionally, we introduced quotes that were not there before, which is
 # OK in most cases, but could change the semantics of the file.
 #
 # Cruel dilemma: we do want the auto-quoting definition of `NEW' when
@@ -889,7 +886,7 @@
 # # ------------------------------
 #
 # This approach is heavily based on traces, but then there is an obvious
-# problem: non expanded code will never be seen/ In particular, the body
+# problem: non expanded code will never be seen.  In particular, the body
 # of a `define' definition is not seen, so on the input
 #
 #        define([idem], [OLD(0, [$1])])
@@ -955,11 +952,11 @@
 # this:
 #
 #  `m4save.m4'
-#    moves the m4 builtins into the `_au_' pseudo namespace
+#    moves the m4 builtins into the `_au_' pseudo namespace,
 #  `unm4.m4'
-#    undefines the builtins
+#    undefines the builtins,
 #  `m4.m4'
-#    restores them
+#    restores them.
 #
 # So `input.m4' is:
 #




reply via email to

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