Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

MISRA.ELIF.DEFINED

Incorrect 'defined' usage in #elif directive.

MISRA-C Rule 19.14 (required): The defined preprocessor operator shall only be used in one of the two standard forms.

This rule is also covered by MISRA.IF.DEFINED.

[Undefined 47]

The only two permissible forms for the defined preprocessor operator are:

defined( identifier )
defined identifier

Any other form leads to undefined behaviour, for example:

#if defined(X > Y) /* not compliant - undefined behaviour */

Generation of the token defined during expansion of a #if or #elif preprocessing directive also leads to undefined behaviour and shall be avoided, for example:

#define DEFINED defined
#if DEFINED(X) /* not compliant - undefined behaviour */

MISRA-C++ Rule 16-1-1 (required): The defined preprocessor operator shall only be used in one of the two standard forms.

This rule is also covered by MISRA.IF.DEFINED.

[Undefined 16.1(4)]

Rationale

The only two permissible forms for the defined preprocessor operator are:

defined ( identifier )
defined identifier

Any other form is a constraint violation, but this is not reported by all compliers.

Example

#if defined ( X > Y ) // Non-compliant — constraint violation

Generation of the token defined during expansion of a '#if' or '#elif' preprocessing directive also leads to undefined behaviour and shall be avoided, for example:

#define DEFINED defined
#if DEFINED(X)              // Non-compliant - undefined behaviour