Welcome to the MISRA discussion forum

I read on the MISRA web site the description of MISRA C2012 that there was also a ISO 26262 compliance guideline/cross reference.
I cannot find that guideline either as free or paid posting. What are the search terms I should use?

Kind regards,
Richard Vance
Software Safety LLC
USA/Mexico

Hi,

Please can anybody help me to understand whether Misra C rules support signed to unsigned and vis-verse data typecasting?

If there is requirement to do some manipulation on signed and unsigned values, then i think it is ok to type-caste. But the requirement given to us says that whenever there is typecasting happening from signed to unsigned and vis-verse, then such incident should be failed.

Thanks in advance,
Deepa

Hi,

Please can anybody help me to understand whether Misra C rules support signed to unsigned and vis-verse data typecasting?

Thanks in advance,
Deepa

The amplification for this rule states:

Quote:In C99 the minimum requirement is that the first 31 characters of external identifiers are significant, with each universal character or corresponding extended source character occupying between 6 and 10 characters.

Quote:In C99 the minimum requirement is that the first 31 characters of external identifiers are significant, with each universal character or corresponding extended source character counting as a single character.

Hi team,
First of all, I want to thank you for supporting people with this amazing forum that is very useful , "Thumbs up".

I have the following File Include Guard:
#ifndef _MYHEADER_H_ // beginning
#define _MYHEADER_H_
...
#endif // end

My question is if File Include Guards have to be applicable/reviewed with the MISRA-C:2004 Rule 19.4 ?

Thanks and Best Regards.
edgartorres0523

Rule 2.4 states that a project should have no unused tag declarations. However in Rule 5.7, a tag name shall be a unique identifier, there is an exception that allows the tag to be the same as the typedef name. You give this example:
typedef struct coord
{
uint16_t x;
uint16_t y;
} coord; /* Compliant by exception */

Can this also be an exception to 2.4 ?

The guidelines proscribe declaring unused types, tags on structures or enums, macros, or labels.

Shouldn't there be a prohibition of undeclared variables, too?

-Stephen H. Westin

Dear

Rule 18.4 mentions +, -, += and -= operators and also ++ operator (both post and pre fix?). -- operator is not mentioned. How to deal with it?

Regards

Hello.

I have a question about rule 21.8.

_Exit Function that were added in C99 also has implementation-defined behavior.

Is this not included?

Best regards,
Kazuhiro Tsukushiro

Hello,

I need to know if my example is compliant :