pcp_reference_guide_v2.5 - Tasking

MISRA−C Rules9−39.1 MISRA−C:1998This section lists all supported and unsupported MISRA−C:1998 rules.See also section 4.7, C Code Checking: MISRA−C, in Chapter Using theCompiler of the User’s Manual.A number of MISRA−C rules leave room for interpretation. Other rules canonly be checked in a limited way. In such cases the implementationdecisions and possible restrictions for these rules are listed.x means that the rule is not supported by the TASKING C compiler.(R) is a required rule, (A) is an advisory rule.1. (R) The code shall conform to standard C, without languageextensionsx 2. (A) Other languages should only be used with an interfacestandard3. (A) Inline assembly is only allowed in dedicated C functionsx 4. (A) Provision should be made for appropriate run−timechecking5. (R) Only use characters and escape sequences defined by ISO Cx 6. (R) Character values shall be restricted to a subset of ISO106460−17. (R) Trigraphs shall not be used8. (R) Multibyte characters and wide string literals shall not beused9. (R) Comments shall not be nested10. (A) Sections of code should not be "commented out"In general, it is not possible to decide whether a piece ofcomment is C code that is commented out, or just somepseudo code. Instead, the following heuristics are used todetect possible C code inside a comment:− a line ends with ’;’, or− a line starts with ’}’, possibly preceded by white space11. (R) Identifiers shall not rely on significance of more than 31characters12. (A) The same identifier shall not be used in multiple namespaces• • • • • • • •