Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

No other identifiers are reserved and if a program declares or defines an identifier in a context in which it is reserved, or defines a reserved identifier as a macro name, the behavior is undefined. Trying to define a reserved identifier may lead to that identifier name conflicting with that used in implementation, which may or may not be detected at compile time

Non Compliant Code

In this example variables are defined with names reserved for the implementation

Code Block
bgColor#FFCCCC

long _Max_Value;
int __length; 

Compliant Solution

The compliant solution uses identifiers that are not reserved

Code Block
bgColor#ccccff

long maxValue;
int length;

Non Compliant Code

In this example, variable beginning with an underscore is defined with implicit global scope.

Code Block
bgColor#FFCCCC
size_t _limit = 100;

unsigned int getValue(unsigned int count){

  size_t i;
  unsigned int result = 0;

  for(i = 0; i < _limit; i++){    
    result++;        
    if(i == count){ 
      break;
    }
  }

}

Compliant Code

In the compliant solution, the variable is declared as static and hence has file scope.

Code Block
bgColor#ccccff
static size_t _limit = 100;

unsigned int getValue(unsigned int count){

  size_t i;
  unsigned int result = 0;

  for(i = 0; i < _limit; i++){    
    result++;        
    if(i == count){ 
      break;
    }
  }

}

Compliant Code

In the compliant solution, the variable is does not begin with an underscore and hence is not reserved.

Code Block
bgColor#ccccff
size_t limit = 100;

unsigned int getValue(unsigned int count){

  size_t i;
  unsigned int result = 0;

  for(i = 0; i < limit; i++){    
    result++;        
    if(i == count){ 
      break;
    }
  }

}

Non Compliant Code

Identifiers with external linkage include setjmp, errno, math_errhandling, va_end.
In the example errno is defined.

Compliant Solution

In the compliant solution, the reserved identifier errno is not used.

Risk Assessment

Use of reserved identifiers may cause incorrect program operation.

Rule

Severity

Likelihood

Remediation Cost

Priority

Level

DCL37-C

low

unlikely

Low

P3

L3

Automated Detection

A module can be written in Compass/ROSE to detect violations of this rule

References

Wiki Markup
\[[ISO/IEC 9899:1999|AA. C References#ISO/IEC 9899-1999]\] Section 7.1.3, "Reserved Identifiers"

...