pcp_reference_guide_v2.5 - Tasking

9−4PCP Reference ManualMISRA−C13. (A) Specific−length typedefs should be used instead of the basictypes14. (R) Use ’unsigned char’ or ’signed char’ instead of plain ’char’x 15. (A) Floating point implementations should comply with astandard16. (R) The bit representation of floating point numbers shall not beusedA violation is reported when a pointer to a floating pointtype is converted to a pointer to an integer type.17. (R) "typedef" names shall not be reused18. (A) Numeric constants should be suffixed to indicate typeA violation is reported when the value of the constant isoutside the range indicated by the suffixes, if any.19. (R) Octal constants (other than zero) shall not be used20. (R) All object and function identifiers shall be declared beforeuse21. (R) Identifiers shall not hide identifiers in an outer scope22. (A) Declarations should be at function scope where possiblex 23. (A) All declarations at file scope should be static where possible24. (R) Identifiers shall not have both internal and external linkagex 25. (R) Identifiers with external linkage shall have exactly onedefinition26. (R) Multiple declarations for objects or functions shall becompatiblex 27. (A) External objects should not be declared in more than onefile28. (A) The "register" storage class specifier should not be used29. (R) The use of a tag shall agree with its declaration30. (R) All automatics shall be initialized before being usedThis rule is checked using worst−case assumptions. Thismeans that violations are reported not only for variables thatare guaranteed to be uninitialized, but also for variables thatare uninitialized on some execution paths.31. (R) Braces shall be used in the initialization of arrays andstructures