From 4c38a43946cd3950a79da42c99448057487f2c53 Mon Sep 17 00:00:00 2001 From: Stepan Kasal Date: Thu, 20 Jan 2005 10:59:55 +0000 Subject: [PATCH] fix AC_DEFINE documentation --- ChangeLog | 5 +++++ doc/autoconf.texi | 5 ++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 36b4ad15..7789758b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2005-01-19 Stepan Kasal + + * 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 * doc/autoconf.texi (Limitations of Usual Tools): Document bug diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 4d42608e..4ee449c7 100644 --- 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.