site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Try this in a terminal: % touch empty.c % cc empty.c -E -dM -o - | sort #define _ARCH_PPC 1 #define _BIG_ENDIAN 1 #define __APPLE_CC__ 5419 #define __APPLE__ 1 #define __BIG_ENDIAN__ 1 #define __CHAR_BIT__ 8 #define __DBL_DENORM_MIN__ 4.9406564584124654e-324 ... Compiler flags and source language can change the built-in definitions. -- Greg Parker gparker@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... What I would like to know is how do you determine what the choices are for these types of #defines? The compiler obviously knows about __GNUC__, and maybe __MWERKS__, but is there a way for me to query the compiler about which ones of these it has defined? (And, what is the proper terminology for these symbols? I would happily google for this info if I knew what to call it.) They're "preprocessor macros" or "preprocessor defines" (not symbols). "built-in" might also be a useful search term. This email sent to site_archiver@lists.apple.com