21-07-2006, 06:00 AM
I am not speaking for the MISRA-C team but here some thoughts:
- regarding compliance and claiming compliance you should consult chapter 4.4 of the MISRA-C-2004 document. I think then is clear.
- a key advantage of MISRA-C-2004 against the old (1998) version is the deviation procedure (see chapter 4.3.2). It is ok to deviate from rules and you are still compliant if you document and comment all deviations i your code.
- there are two types of deviations, project deviation and specific deviation. again see 4.3.2 for details.
- especially looking at rule 1.1 which you are referring to there were modifications between MISRA-C 2004 and 1998. (plus the deviation procedure). Now it is (IMO) legal and you are still misra-compliant if you use specific extensions of your embedded comipler AS LONG as you document them and comment why.
In essence this is what extensions are for. You WANT to use the optimizations of your platform and MISRA-C-2004 does not block this.
kind regards,
Bernhard.
- regarding compliance and claiming compliance you should consult chapter 4.4 of the MISRA-C-2004 document. I think then is clear.
- a key advantage of MISRA-C-2004 against the old (1998) version is the deviation procedure (see chapter 4.3.2). It is ok to deviate from rules and you are still compliant if you document and comment all deviations i your code.
- there are two types of deviations, project deviation and specific deviation. again see 4.3.2 for details.
- especially looking at rule 1.1 which you are referring to there were modifications between MISRA-C 2004 and 1998. (plus the deviation procedure). Now it is (IMO) legal and you are still misra-compliant if you use specific extensions of your embedded comipler AS LONG as you document them and comment why.
In essence this is what extensions are for. You WANT to use the optimizations of your platform and MISRA-C-2004 does not block this.
kind regards,
Bernhard.