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.
Consider this:
#ifndef GUARD_H
#define GUARD_H
...
#endif GUARD_H
rather than:
#ifndef GUARD_H
#define GUARD_H
...
#endif // GUARD_H
Often I see at the #endif an ‘identifier’ commented out but without commenting it it still works.
Is everything after the #endif ingnored or…?
No, this is not valid C++: it is ill-formed. There can be no tokens between the
# endifand the newline that terminates the preprocessing directive line.If you want to restate the condition from the
#ifdirective, you can do so in a comment:However, this is really just redundant, especially for inclusion guards: if it’s the last
#endifin a header file, it’s almost certainly there to end the#ifdefused at the top to prevent multiple inclusion, no?In other places where you may have multiple nested levels of conditional directives, this might be useful, but even then it is often preferable to refactor the code to make it simpler or more straightforward.