RefreshYourBasics - Misra C

A project with unused type declarations is compliant or not with MISRA?

For example,

int16_t unusedtype ( void )

{

typedef int16_t local_Type;

return 67;

}

• Compliant

• Non-compliant

The following macro example comes under

void use_macro ( void ) {

#define SIZE 4

#define DATA 3

use_int16 ( SIZE );

}

Assertion: A project containing unused macro declaration will lead to code

redundancy and unclear.

Reason: The unused macro will give an advisory action and leads to un-necessary memory space consumption

• The Assertion and the Reason are correct but the Reason is not the correct explanation of the Assertion.

• Both the Assertion and the Reason are correct and the Reason is the correct explanation of the Assertion.

• Our Assertion is true but the Reason is false.

• The statement of the Assertion is false but the Reason is true.

• Both the statements are false.

#define DIV2(X) ( ( X ) / 2 )

void f ( void ) {

static uint16_t x = DIV2 ( 10 );

}

Macro to initialize with Static storage function call comes under

• Compliant because call not permitted

• Non- Compliant because call permitted

• Compliant because call permitted

• Non-Compliant because call not permitted

The preprocessor will assume that the macro identifier has a value of zero if

• Macro identifier has been defined and not used in preprocessor directive

• Macro identifier has not been defined and used in preprocessor directive

• Macro identifier has been defined and used in preprocessor directive

Unintentional removal of code occurs if the source line containing a // comment ends with which of the following character?

• \

• /

• *

• /*

Which of the following is not compliant with MISRA?

• int16_t y[ 3 ][ 2 ] = { 1, 2, 0, 0, 5, 6 };

• int16_t y[ 3 ][ 2 ] = { { 1, 2 }, { 0 }, { 5, 6 } };

• int16_t y[ 3 ][ 2 ] = { { 1, 2 }, { 0, 0 }, { 5, 6 }

Which of the following is NOT compliant with MISRA?

• ( bool_t ) false

• ( int32_t ) 3U

• ( bool_t ) 3U

• ( bool_t ) 0

Rule 10.8 The value of a composite expression shal l not be cast to a diff erent

essential type category or a wider essential type. Which of the below satifies this rule?

• ( uint16_t ) ( s32a + s32b )

• ( uint16_t ) s32a

• ( uint32_t ) ( u16a + u16b )

switch ( x == 0 )

{

case false:

y = x;

break;

default:

y = z;

break;

}

Is the above code by using a switch expression with boolean type compliant with MISRA?

• Compliant

• Non-compliant

uint16_t func ( uin t16_t para1 )

{

return para1;

}

uint16_t x;

void discarded ( uint16_t para2 )

{

func ( para2 ); //Line 1

( void ) func ( para2 ); //Line 2

x = func ( para2 ); //Line 3

}

Which line is not compliant with MISRA?

• Line 1

• Line 2

• Line 3