You must follow MISRA C rules when you generate MISRA C
compliant code using Object Execution Framework (OXF).
The violations listed are for OXF and for the code generated
using the MISRA98 profile.
- Rule 18 (Advisory) - violated by the use of system constants in
the file RiCOSNT.h (WAIT_FAILED, INFINITE).
- Rule 118 (Required) - violated by the use of malloc/realloc/free
in the files RiCHdlCls.c and RiCOx.c.
- Rule 107 (Required) - violated by the dereferencing of a null
pointer in the definition of ricoffsetof.
- Rule 45 (Required) - violated in a number of places in the generated
code. In some of these cases, there is an inline comment that explains
that this is a known violation and explains why this does not affect
the quality of the code.
- Rule 20 (Required) - in the code generated for relations, functions
are sometimes used before they are declared.
- Rule 23 (Advisory) - functions related to statecharts and timeouts
are used only in the file in which they are generated but are not
specified as "static".
- Rule 107 (Required) - there are a number of places in the generated
code that refer to the pointer "me" without first checking that the
pointer is not NULL.