Welcome to the MISRA discussion forum

Hello.

Are there any code metrics defined by MISRA?

Thanks.

I have a function returning a pointer to an array, not an uncommon situation I would think.
How can I reference elements in that array without violating Rule 17.4 ?.
1. Indexing is not compliant as the return type is not an array.
2. Pointer arithmetic is not compliant.
So it looks like returning pointers to arrays is effectively banned by this rule, is that the case?.

"Before preprocessing, a null statement shall only occur on a
line by itself; it may be followed by a comment provided that
the first character following the null statement is a white-space
character." in this rule,why "Before preprocessing"is used as a condition?
Thanks!

void func()
{
int errno;//does even declaration of errno violates rule20_5,errno is user defined?
}

Should literal 0 be exempt from rule 10.1? True, rule 10.6 requires a 'U' suffix in this case. However, what about in regards to rule 10.1 by itself?

According to the rule 20.5, error indiaction facility should not be used even if it is well defined.
1)Is it mean that we should not declare the identifier(function and variable) with the name "errno"?
2)As per the standard library for linux "errno" MACRO is defined to function pointer call and for Visual C++ it is extern variable declaration. So does usage of "errno"(i.e. function call) on linux also violates the rule 20.5?

We bought a single license for MISRA C document. We are developping an internal tool to check MISRA rules, is it possible to use the description of each rule in the helper of the tool ?
Or exist any restriction also in the usage of the rules description ?

Giacomo

The wording of advisory #12.6 indicates expressions other than effectively boolean ones are permitted as the conditional argument to "?:". Was this wording an oversight? In three other circumstances, the guidelines insist on effectively boolean expressions and it seems unintuitive to not require such in this case as well.

I didn't find any limitation in MISAR AC* in the usage of matlab lenght identifier.

Where I am wrong ?

Giacomo

Do rules #6.4 and 6.4 apply to unnamed bit fields? I would think, since the such fields are unnamed, one would not easily access them.