"Thierry" <[EMAIL PROTECTED]> writes: > Assuming I'm building the test.cpp file only with the compiler flag > -DHELLO_THERE, how come in "hello.h", it's not even aware of > HELLO_THERE.
If "test.cpp" in fact starts with the '#include "hello.h"' and if "hello.h" starts with '#ifdef HELLO_THERE', then what you've described is extremely impobable. What's more likely is that you have some other '#includes' before "hello.h", and it is likely that one of them has '#undef HELLO_THERE', which "wins" over the command line because it is later in the input stream. > Any help please? You should be able to find out if that's the case by examining the output from: g++ -DHELLO_THERE -E -dD test.cpp Cheers, -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. _______________________________________________ Help-gplusplus mailing list Help-gplusplus@gnu.org http://lists.gnu.org/mailman/listinfo/help-gplusplus