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

plugin_functions.xml: Using custom functions

The plugin_functions.xml file is created when you use the --kast-library option with kwcreatechecker.

plugin_functions.xml requires updating if:

Example 1: Using the default function name and class

The checkers.xml file contains the following KAST expression:

<pattern>

        // Stat [ myFunc() ]

</pattern>

And the default class is used in MyFunc.java.

Consequently, there's no need to update the function name in plugin_functions.xml.

See the diagram below:

Example 2: Using a different function name

The checkers.xml file contains the following KAST expression:

<pattern>

        // Tree [ BoolTypeJCustom() ]

</pattern>

But the default class name is used in MyFunc.java.

See diagram below:

Consequently, we'll need to update the function name in plugin_functions.xml to:

<pattern>

        // Tree [ BoolTypeJCustom() ]

</pattern>

But no update to the MyFunc.java file is required.

See also Java custom functions.