On Apr 7, 2004, "Gary V. Vaughan" <address@hidden> wrote:
Agreed. Autoconf generates a config.h that encourages #ifdef/#ifndef.
And then it promotes the use of #if. I recall discussions about this
in the autoconf list years ago, and there was a conscious decision to
replace most uses of #ifdef with #if in the documentation, but I can't
find any wording that explicitly recommends the use of #if over
#ifdef. Oh well...
Tree version: address@hidden/libtool--devo--1.0
CVSROOT: /cvsroot/libtool
TIMESTAMP: 1.1477 2004/04/13 15:30:10
Module name: /cvsroot/libtool/libtool
Changes by: address@hidden
Log Message:
* libltdl/lt__pre89.h, libltdl/ltdl.c, libltdl/ltdl.h, libltdl/argz.c,
libltdl/argz.h, libltdl/lt__glibc.h, libltdl/lt_dlloader.h,
libltdl/lt__dirent.c, libltdl/lt__dirent.h, libltdl/lt__private.h,
libltdl/lt__alloc.c, libltdl/lt__alloc.h, libltdl/lt_system.h,
libltdl/loader-dld_link.c, libltdl/loader-dlopen.c,
libltdl/loader-dyld.c, libltdl/loader-loadlibrary.c,
libltdl/loader-shl_load.c, libltdl/lt_error.h, libltdl/lt_mutex.h:
Autoconf either defines to 1 or undefs the discovery macros it
puts in config.h, and many (non-GNU) compilers throw a spurious
warning when testing an #undef macro with #if. For consistency,
while we are touching all these lines, use defined(MACRO) style
throughout.
Reported by Bob Friesenhahn <address@hidden>