Page 1 of 1

Rule 2.5 vs. include guards

Posted: Mon Feb 27, 2017 11:54 am
by sg2
It is not completely clear what is meant by use of a macro in Rule 2.5. There is definition of a use of an expression in the Glossary, but not of a macro.
If taken literally, rule 2.5 means that standard include guards are forbidden:

#ifndef HEADER_H
#define HEADER_H // Not used unless another #ifndef is encountered somewhere inside

Re: Rule 2.5 vs. include guards

Posted: Thu Mar 30, 2017 9:01 am
by misra-c
Your example is compliant with rule 2.5. The #ifndef HEADER_H is considered to be a use of the macro name, even though it appears before the #define.