02-03-2010, 11:32 AM
02-03-2010, 02:54 PM
I always create a list with frequently used pragmas with the rationale for their use, and put a short reference in the C source.
For seldom used pragmas, I put an extensive (§+ line) comment in the source, with the rationale for this single use.
It has satisfied all auditors to date.
FWIW,
Johan
For seldom used pragmas, I put an extensive (§+ line) comment in the source, with the rationale for this single use.
It has satisfied all auditors to date.
FWIW,
Johan
02-03-2010, 03:46 PM
cheers Johan,
I'll give that a shot
Matt
I'll give that a shot
Matt
10-03-2010, 10:41 AM
MISRA is not concerned about the format of the documentation, just that the use (and the justification for the use) of each #pragma directive is recorded.
The method of documentation should be specified in the Software Management Plan (MISRA-C:2004 Section 4.1) and Compliance Matrix (MISRA-C:2004 Section 4.3.1).
The method of documentation should be specified in the Software Management Plan (MISRA-C:2004 Section 4.1) and Compliance Matrix (MISRA-C:2004 Section 4.3.1).