MISRA Discussion Forums
Why is the code below cited for violation of MISRA 13.6 - 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.13 Control Statement Expressions (https://forum.misra.org.uk/forumdisplay.php?fid=40)
+---- Thread: Why is the code below cited for violation of MISRA 13.6 (/showthread.php?tid=812)



Why is the code below cited for violation of MISRA 13.6 - kalpak - 03-03-2011

Why is the last code line (array element initialization) in the code below being cited for 13.6 violation by Crystal Revs MISRA checker:
Code:
/*Test code for Crystal revs MISRA rule 13.6 */
typedef unsigned char uint8_t
void InitArray(void);

#define LCD_NUM_OF_COLS 2u
#define LCD_NUM_OF_ROWS    10u
uint8_t Test_Array[LCD_NUM_OF_COLS][LCD_NUM_OF_ROWS];

void InitArray(void)
    {
    uint8_t row_index = 0u;
    uint8_t col_index = 0u;    
    for (col_index = 0u; col_index < LCD_NUM_OF_COLS; col_index++)
        {
        for (row_index=0u; row_index < LCD_NUM_OF_ROWS; row_index++)    
            {
            /*    make each element of the array the char NULL    */
            Test_Array[col_index][row_index] = 0u;    
            }    
        }
    }

thanks,
kalpak


Re: Why is the code below cited for violation of MISRA 13.6 - misra-c - 07-03-2011

The code example does not appear to violate Rule 13.6. There is a missing ';' character at the end of the typedef but this would not explain the diagnostic message from your tool.

MISRA does not provide guidance on specific tools so you should contact your tool provider for an explanation.


Re: Why is the code below cited for violation of MISRA 13.6 - kalpak - 08-03-2011

Thanks,
that ";" was forgotten while creating a minimum demo code to test.
And even after adding that ";", the warning persists.
Unfortunately the vendor of Crystal Revs was informed of this 2 weeks ago but they have not replied yet.