[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: #if vs. #ifdef -- again (was: AC_CHECK_SIZEOF failing on undefined H

From: nash
Subject: Re: #if vs. #ifdef -- again (was: AC_CHECK_SIZEOF failing on undefined HAVE_STDINT_H with -Werror)
Date: Tue, 15 Aug 2006 11:25:32 -0400

Really? C99 seems to do so (section 6.10.1). Perhaps I'm reading more
into it than is actually there, though.


On 8/15/06, Andreas Schwab <address@hidden> wrote:
nash <address@hidden> writes:

> Wouldn't it be preferrable to use #if so that a config.h token could
> be an expression that variously evaluates to T/F depending on other
> stuff? For example,
> In config.h somewhere:
>  #define HAVE_WORKING_MMAP (defined(HAVE_MMAP) && defined(HAVE_MUNMAP))

This won't work anyway, the C standard does not define the behaviour of
defined in expanded tokens.


Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]