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

STRONG.TYPE.ASSIGN.ZERO

Assignment of zero to strong type variable

The STRONG.TYPE family of checkers detects situations in which programmer-enforced strong typing (type-defined abstract types) is broken or ignored, allowing the underlying ANSI type semantics to dominate.

The STRONG.TYPE.ASSIGN.ZERO checker finds assignments of zero to a variable of a strong type. In this rule, zero is defined as any zero constant that has not been cast to a strong type. For example, the checker considers the following to be zero:

  • 0L
  • (int)0

The checker considers the following examples not to be zero:

  • (SPEED)0
  • (SPEED*)0

Vulnerability and risk

A compiler following the ANSI standard won't report a warning for this sort of issue, as it checks only the underlying types, not the surface, or programmer-defined, types. As a result, it's possible that a logic error can occur.

Vulnerable code example

1 typedef int Weight;
2 
3 int main() {
4   Weight ElephantW;
5   ElephantW = 0; 
6   return 0;
7 }

Klocwork flags line 5, in which zero is assigned to strong type ElephantW.