fix AC_DEFINE documentation

diff --git a/ChangeLog b/ChangeLog
index 36b4ad158ebe8ca46730a654239f98ace5c82879..7789758bdebaa14137d8174ef1d3ebb0a720bda6 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2005-01-19  Stepan Kasal  <kasal@ucw.cz>
+
+       * doc/autoconf.texi (Defining Symbols): Delete the false comment that
+         you cannot use AC_DEFINE to define macros containing `[' or `]'.
+
 2005-01-13  Paul Eggert  <eggert@cs.ucla.edu>
 
        * doc/autoconf.texi (Limitations of Usual Tools): Document bug

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 4d42608eb940ecf3f729b806270910d767f221d6..4ee449c7c4370d03e0fdf2cd4fc272db8e709ee0 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -7204,9 +7204,8 @@ output.
 Define the C preprocessor variable @var{variable} to @var{value} (verbatim).
 @var{value} should not contain literal newlines, and if you are not
 using @code{AC_CONFIG_HEADERS} it should not contain any @samp{#}
-characters, as @command{make} tends to eat them.  To use a shell variable
-(which you need to do in order to define a value containing the M4 quote
-characters @samp{[} or @samp{]}), use @code{AC_DEFINE_UNQUOTED} instead.
+characters, as @command{make} tends to eat them.  To use a shell variable,
+use @code{AC_DEFINE_UNQUOTED} instead.
 @var{description} is only useful if you are using
 @code{AC_CONFIG_HEADERS}.  In this case, @var{description} is put into
 the generated @file{config.h.in} as the comment before the macro define.