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

JD.UN.MET

JD.UN.MET occurs if no call for method is found in the analyzed code. (This checker is triggered only by non-private methods that were not overloaded, or did not overload something).

Vulnerability and risk

Unused methods can be used as back doors. They also increase code footprint in memory. Additionally, they increase the size of source code which decreases maintainability.

Mitigation and prevention

Remove unused methods. Be careful when removing methods. Make sure the method was not designed for extensibility or is not a library method that may be used by code that is not part of the code you are analyzing with Klocwork.

Example 1

9      static class MyClass {
10         void foo(){
11             System.err.println("Hello, World!");
12         }
13     }

JD.UN.MET is reported for method declaration on line 10: Method 'foo()' is never called in the analyzed context.

Related checkers