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

LS.CALL.STRING

Suspicious use of non-localized string in GUI function

Localized string call is used to check for the use of non-localized string directly (in the function argument) in customer facing functions.
Important: This is an experimental checker.

Code example

1    int main()
2    {
3        print_string(“Non-Localized String”); // Line 3. LS.CALL.STRING
4        return 0;
5    }
Klocwork produces a Localized String report for line 3 indicating that there is a potential call to GUI functions using a non-localized string.
Note: In order to detect the issue, the above code should be run with a KB that has the following record: print_string - xLS 1:$1:1

Related checkers