Boolean in ifdef: is "#ifdef A && B" the same as "#if defined(A) && defined(B)"?

c++ c-preprocessor conditional-compilation
criddell picture criddell · Aug 21, 2009 · Viewed 86.4k times · Source

In C++, is this:

#ifdef A && B

the same as:

#if defined(A) && defined(B)

?

I was thinking it wasn't, but I haven't been able to find a difference with my compiler (VS2005).

Answer

Evan Teran picture Evan Teran · Aug 21, 2009

They are not the same. The first one doesn't work (I tested in gcc 4.4.1). Error message was:

test.cc:1:15: warning: extra tokens at end of #ifdef directive

If you want to check if multiple things are defined, use the second one.

Related questions

Use #ifdefs and #define to optionally turn a function call into a comment

Is it possible to do something like this #ifdef SOMETHING #define foo // #else #define foo MyFunction #endif The idea is that if SOMETHING is defined, then calls to foo(...) become comments (or something that doesn't get evaluated or compiled), otherwise …

Read More
How do I check if one of multiple macros is defined in a single #ifdef?

I have some C++ code, and want to perform an action if the __APPLE__ or __linux macros are defined. If I did it as a normal if conditional, it would be easy using ||: if (something || something) { .. code .. } But as of …

Read More
#elseif vs #elif (C/C++ preprocessor)

I have found that writing #ifdef ... #elseif defined(...) #else #endif always results in using either the #ifdef or the #else condition, never the #elseif. But substituting #elif causes it to work as expected based on what's defined. What convoluted purpose, …

Read More