Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Rule 3.4: All uses of the #pragma directive shall be...
#1
Hi,
What exactly does this rule mean?
How do i document a #pragma?

thanks,

Matt
<t></t>
Reply
#2
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
<r>Johan Bezem<br/>
Email: <EMAIL email="[email protected]">[email protected]</EMAIL><br/>
Tel: +49 172 5463210<br/>
Web: <URL url="http://www.bezem.de/">http://www.bezem.de/</URL></r>
Reply
#3
cheers Johan,

I'll give that a shot

Matt
<t></t>
Reply
#4
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).
Posted by and on behalf of the MISRA C Working Group
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)