Welcome to the MISRA discussion forum

Hello,

Pls. guide on the process and criteria for the "MISRA" membership.

Link: http://www.misra.org.uk/Links/tabid/63/Default.aspx --> Useful links --> MISRA Members

Hello,

Pls. guide on the process and criteria on getting any tool/ parent company listed in the list of "Tools supporting MISRA C..." under Category "Useful links" on "MISRA" website..

According to the Exception to 11.3, it is permissible to convert a pointer to object into pointer to char, signed char, or unsigned char. There doesn't appear to be an Example within the MISRA document, but I believe it would look like

Dear Sirs,
Hearing from colleague attended IQPC 4th International Conference “Applying ISO 26262”, I got to know MISRA is now working on Safety Case Guideline. Is there any public available draft of this ? I’m interested in how security issue is discussed within the case.

Thanks in advance,
T. Kuwayama, OTSL Inc.

Is the following example intended to be a violation of Rule 11.9?

Why in SLSF there are no role to garantee that expression in acgtion and condition are written in such a way the C code is portable from 32 and 16 bit microcontroller ?

GG

The rule 10.1 and 10.4 of MISRA 2004 is vital for porting C code from 32 to 16 bit micro.
Why AC set this role to reccomended and not mandatory ?

GG

I have a question for Amplification of Rule 3.2.

Your guideline has the following description in item "Amplification" of Rule 3.2.

"If the source file contains multibyte characters, they are converted to the source character set before any splicing occurs."

However, I did not understand the aim of this description well. Will you explain the details?

Especially, I do not understand why "multibyte characters" are related to "splicing".

Do you intend to explain the supporting case ,"multibyte characters including "\" character"?

I suppose it as follows.

"\" character included in "multibyte characters" is different from "line-splicing \",so there are not mixed.

For example,
uint16_t x=0; // 表
if( b)
{
x++;
}

Even If this character"表" incudes "\" character,
this "\" is not a meaning of "line-splicing".


Is this correct?

Please teach me.

Best Regards,
Kumiko Itoh

I have a customer for our compiler who is asking this question:

Rule 5.2 deals with identifiers declared with block scope that hide identifiers declared at an outer block, or file, scope. It does not apply to identifiers declared in other translation units.

extern void SerialMaster_task(void *p_arg);

Warning[Pm017]: symbol hides parameter "p_arg" (declared at line 380) - identifiers in an inner scope shall not use the same name as an identifier in an outer scope, and therefore hide the identifier (MISRA C 2004 rule 5.2)

A parameter in the *declaration* of an external subroutine does not define a symbol in the current context.

---
Can you elaborate about why the source line above invokes MISRA C 2004 rule 5.2?

Dave Bailey
IAR Systems

This rule is related to "#undef".
But "See also" of this rule does not contain "Rule 20.5 # undef should not be used".
I think Rule 20.5 should be included in "See also".

Is it correct?

Best Regards.