pcp_reference_guide_v2.5 - Tasking

9−6PCP Reference ManualMISRA−C49. (A) Tests of a (non−Boolean) value against 0 should be madeexplicit50. (R) F.P. variables shall not be tested for exact equality orinequality51. (A) Constant unsigned integer expressions should notwrap−around52. (R) There shall be no unreachable code53. (R) All non−null statements shall have a side−effect54. (R) A null statement shall only occur on a line by itself55. (A) Labels should not be used56. (R) The "goto" statement shall not be used57. (R) The "continue" statement shall not be used58. (R) The "break" statement shall not be used (except in a"switch")59. (R) An "if" or loop body shall always be enclosed in braces60. (A) All "if", "else if" constructs should contain a final "else"61. (R) Every non−empty "case" clause shall be terminated with a"break"62. (R) All "switch" statements should contain a final "default" case63. (A) A "switch" expression should not represent a Boolean case64. (R) Every "switch" shall have at least one "case"65. (R) Floating point variables shall not be used as loop counters66. (A) A "for" should only contain expressions concerning loopcontrolA violation is reported when the loop initialization or loopupdate expression modifies an object that is not referencedin the loop test.67. (A) Iterator variables should not be modified in a "for" loop68. (R) Functions shall always be declared at file scope69. (R) Functions with variable number of arguments shall not beused