Rule 16.9 - Error in code example - Printable Version +- MISRA Discussion Forums (https://forum.misra.org.uk) +-- Forum: MISRA C (https://forum.misra.org.uk/forumdisplay.php?fid=4) +--- Forum: MISRA-C: 2004 rules (https://forum.misra.org.uk/forumdisplay.php?fid=17) +---- Forum: 6.16 Functions (https://forum.misra.org.uk/forumdisplay.php?fid=47) +---- Thread: Rule 16.9 - Error in code example (/showthread.php?tid=683) |
Rule 16.9 - Error in code example - William Forbes - 24-10-2009 The code in the normative text of rule 16.9 is: Code: if (f) /* not compliant - gives a constant non-zero value which is Code: if (f) /* not compliant - gives a constant non-zero value which is Note - the opening brace was inside the comment. A trivial error but maybe it should get corrected? Re: Rule 16.9 - Error in code example - jbezem - 27-10-2009 You are, of course, correct. And since this error has not been corrected in TC1, it should be put on the list for TC2 or C3, depending on which will be first ;-) To the moderator: Is there a defined procedure for reporting such errors? Also for the Exemplar Suite (where I found at least one small error)? Regards, Johan Re: Rule 16.9 - Error in code example - misra-c - 10-11-2009 This is indeed a typo and was corrected in edition 2 of MISRA-C:2004. The procedure for reporting errors, including errors in the exemplar suite, is to post to this forum. Re: Rule 16.9 - Error in code example - William Forbes - 11-11-2009 Hi I thought MISRA-C:2004 v2 was simply v1 + TC1. There is no mention of this typo in TC1 so I assumed it still stood! What other silent changes were incorporated into v2? Is there a change log? Cheers Bill Forbes Re: Rule 16.9 - Error in code example - misra-c - 20-11-2009 Please see the reply to a similar question at http://www.misra.org.uk/forum/viewtopic.php?f=74&t=985 There is no change log at present. |