02-03-2010, 11:32 AM
Hi,
What exactly does this rule mean?
How do i document a #pragma?
thanks,
Matt
What exactly does this rule mean?
How do i document a #pragma?
thanks,
Matt
<t></t>
Welcome to the new MISRA discussion forum, if you were previously a member of our forums you may need to reset your password.
Rule 3.4: All uses of the #pragma directive shall be...
|
02-03-2010, 11:32 AM
Hi,
What exactly does this rule mean? How do i document a #pragma? thanks, Matt
<t></t>
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
<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>
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).
Posted by and on behalf of the MISRA C Working Group
|
« Next Oldest | Next Newest »
|