Sure, but you could just as well just #define it, since you know what you're compiling for. The more interesting question is how to determine, if you are a 32-bit app, whether you are running on a 64-bit processor.Originally Posted by cyberfish
Sure, but you could just as well just #define it, since you know what you're compiling for. The more interesting question is how to determine, if you are a 32-bit app, whether you are running on a 64-bit processor.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
Salem, the quote was talking not about standard C/C++ but about standard UNIX. Do "POSIX or X/Open" require any macros for identification of compatible systems? If not, what am I missing? Is SF just wrong?
How would you #define it if the same source is preprocessed and compiled for both 32-bit and 64-bit?
But what is a 32-bit app? What makes a program compatible with each bit-width?
And why wouldn't cyberfish's detection work for that?
