MISRA violation 10.1 - From stateflow transition if statement generated without explicit comparison

MISRA violation 10.1. From a state transition in stateflow the generetd code results as follow:

if ( bolean_variables)

{ ...

}

else

{...

}

instead

if(TRUE = bolean_variables)

{..

...

Answer 1

[Angelo Yeo]

Can you elaborate what your pain point is? Why do you want to follow MISRA Rule 10.1 when your C code is auto-generated?

As you can see in MISRA C:2012 (I am asssuming you are trying to follow MISRA C 2012), Rule 10.1 becomes advisory (not "required" anymore) when it comes to an auto-generated C code.

[Francesco]

Yes, you'll right about the MISRA rule but I would like to avoid to write an argumentation for all of these advisory. There are a lot of advisory releted to rule 10.1 ... I was expected to fix it in the model, maybe acting on the code generation settings. If it is possible...

[Angelo Yeo]

It's great that you work hard to get rid of all the violations. But in my humble opinion, it's not going to be worked out perfectly as this is an "advisory" rule for auto-generated codes.