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

Popular posts from this blog

css - Text drops down with smaller window -

php - Boolean search on database with 5 million rows, very slow -

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -