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.
I found these lines:
#undef TAG
#define kTAG @"TestRegistration///: "
#define TAG kTAG
If TAG never been used, why do they #undef TAG before they #define it?
There’s no reason to do it if the macro wasn’t previously defined. If you expect the macro could be previously defined, though, it’s a good idea to undef it first because it makes it clear to the reader of the code that you intend to override the previously-set value of the macro (if any).
If you don’t expect the macro could already be defined, you shouldn’t use the undef first. That way, if it is (surprisingly!) already-defined, you’ll get a warning.