A macro is a preprocessor right. Sometimes we set things right sometimes we don’t.
Wouldn’t it be nice to once in a while expand the macro and see how it works?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
You can do this with most compilers, e.g. with gcc:
this just runs the preprocessor and then stops, giving you the pre-processed output on stdout.
If you’re using Xcode though you don’t even need to do this – depending on what version of Xcode you’re using you can just select
Preprocessfrom theBuildmenu (that’s what its called in Xcode 3.x – if you’re using Xcode 4 it may have been moved/renamed). See: Xcode Preprocessor Output