Index: ChangeLog
===================================================================
RCS file: /cvsroot/autoconf/autoconf/ChangeLog,v
retrieving revision 1.2470
diff -u -r1.2470 ChangeLog
--- ChangeLog	13 Jan 2005 21:03:50 -0000	1.2470
+++ ChangeLog	19 Jan 2005 18:28:08 -0000
@@ -1,3 +1,8 @@
+2005-01-19  Stepan Kasal  <address@hidden>
+
+	* 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  <address@hidden>
 
 	* doc/autoconf.texi (Limitations of Usual Tools): Document bug
Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.863
diff -u -r1.863 autoconf.texi
--- doc/autoconf.texi	13 Jan 2005 21:03:11 -0000	1.863
+++ doc/autoconf.texi	19 Jan 2005 18:28:09 -0000
@@ -7204,9 +7204,8 @@
 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.