c - Any reason to define a header-guard to 1? -
occasionally observe such header guards:
#ifndef foo #define foo 1 ... #endif // foo but learned way:
#ifndef foo #define foo ... #endif // foo is define 1 old relict compiler?, harm nowadays? way now?
Comments
Post a Comment