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.MEMB.NON_STATIC

Non-static member function does not use other non-static members of the same class.

MISRA-C++ Rule 9-3-3 (required): If a member function can be made static then it shall be made static, otherwise if it can be made const then it shall be made const.

This rule is also covered by MISRA.MEMB.NON_CONST.

Rationale

Declaring a member function static or const limits its access to the non-static data members. This helps to prevent unintentional modification of the data, and facilitates compliance with Rule 7—1—1.

Example

class A
{
public:
   int16_t f1 ( ) // Non-compliant — can be const
   {
      return m_i;
   }

   int16_t f2 ( ) // Non-compliant — can be static
   {
      return m_s;
   }

   int16_t f3 ( ) // Compliant — cannot be const or static
   {
      return ++m_i;
   }
private:
   int16_t m_i;
   static int16_t m_s;
};