Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> I suggest the following change:
Thanks. I reworded it slightly, as footnotes should be avoided
technical manuals (this isn't comparative English literature :-), and
installed this patch.
2006-05-27 Ralf Wildenhues <[EMAIL PROTECTED]>
and Paul Eggert <[EMAIL PROTECTED]>
* doc/autoconf.texi (autoheader Invocation): The first argument to
`AC_DEFINE_UNQUOTED' need not be a literal. Mention the
alternatives and clear up the language a bit.
--- doc/autoconf.texi.~1.1028.~ 2006-05-26 19:54:33.000000000 -0700
+++ doc/autoconf.texi 2006-05-27 15:17:44.000000000 -0700
@@ -2885,13 +2885,14 @@ arguments are given, the first one is us
@command{autoheader} creates @file{config.h.in}.
In order to do its job, @command{autoheader} needs you to document all
-of the symbols that you might use; i.e., there must be at least one
[EMAIL PROTECTED] or one @code{AC_DEFINE_UNQUOTED} call with a third
-argument for each symbol (@pxref{Defining Symbols}). An additional
-constraint is that the first argument of @code{AC_DEFINE}
-or @code{AC_DEFINE_UNQUOTED} must be a
-literal. Note that all symbols defined by Autoconf's builtin tests are
-already documented properly; you only need to document those that you
+of the symbols that you might use. Typically this is done via an
[EMAIL PROTECTED] or @code{AC_DEFINE_UNQUOTED} call whose first argument
+is a literal symbol and whose third argument describes the symbol
+(@pxref{Defining Symbols}). Alternatively, you can use
[EMAIL PROTECTED] (@pxref{Autoheader Macros}), or you can supply a
+suitable input file for a subsequent configuration header file.
+Symbols defined by Autoconf's builtin tests are already documented properly;
+you need to document only those that you
define yourself.
You might wonder why @command{autoheader} is needed: after all, why
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
