Include AnalysisThe Include Analysis report shows the dependencies between a file and its directly or transitively included header files. For each of the symbols used in a particular file, the report determines what other symbol definitions / declarations are necessary, and then analyzes how these definitions / declarations are picked up through the inclusion of header files.
By helping you analyze the Include Analysis report enables you to optimize #include hierarchies, improve compiler times, and make code reuse easier.
Similar FunctionsThe Similar Functions report finds functions that have name and/or structure-based similarities. This information supports refactoring efforts that try to consolidate similar code. Identification of similar functions is also useful when checking whether bug fixes to one function might apply elsewhere.
The formula that combines these individual similarity scores can be user specified. By default, the report lists functions that have either 90% similar name and 90% similar fanout, or 90% similar name and 90% similar metrics values, or 90% similar fanout and 90% similar metrics values. Through the Similarity Formula dialog, this formula can be changed.
The report can be run in two ways, When it's invoked through the Reports menu, it checks for all functions in the project for similar functions. In this case, minimum values can be defined for the name lengths, cross reference fanout and McCabe Cyclomatic Complexity, so that functions with little content are not considered.
Alternatively, functions similar to any specific function can be identified by running the Similar Functions report through the Analyze dialog. This dialog selection is available whenever the Analyze dialog is focused on a non-library function.
Reflection AnalysisThe Reflection Analysis report invokes an advanced analysis of Java method calls made through the reflection API (java.lang.reflect). The analysis locates all calls to "invoke()" in the project and then attempts to trace back to the methods that have been selected as the target for that dynamic call. The report lists any locations of invoke() where the analysis was unable to determine the method selected. This report and the associated analysis are only available for Java projects.
Once the report has been run, the analysis results are integrated with the current session's database. Dynamic calls relationships are added between the location where the method was selected (the so-called requester of the dynamic call) and the targets. These relationships can be visualized in the Graph window; any of the views that show normal calls relationships also show dynamic calls.
JNI Calls AnalysisThe JNI Calls Analysis report analyzes mixed Java and C/C++ projects to identify the use of JNI (Java Native Interface) to implement Java objects in compiled C/C++ binaries. The analysis locates all Java functions whose name starts with "native" and then attempts to match them to a C/C++ function with the same name. The report indicates how many matches are found. This report and the associated analysis are only available for projects that contain both Java and C/C++ data sources.
Once the report has been run, the analysis results are integrated with the current session's database. Calls relationships are added from the Java function to the matching C/C++ function. These relationships can be visualized in the Graph window; you're able to follow the full calling hierarchy from the higher level Java code down into the lower level C/C++ implementations.