Analyzing how a CMake-based project has changed over time (Part 4 of 5). This article focuses on creating a trendline of changes to avoid the artifacts caused by non-linear history.
Author: Natasha Stander
CMake Compare Part 3: Violation Trends
Analyzing how a CMake-based project has changed over time (Part 3 of 5). This article focuses on creating a CodeCheck Violation trend line from multiple databases representing different time points in GitAhead.
CMake Compare Part 2: Automation
Analyzing how a CMake-based project has changed over time (Part 2 of 5). Using command-line tools to create hundreds of comparison databases and constructing a trend line of analysis errors over time
CMake Compare Part 1: Creation
Analyzing how a CMake-based project has changed over time (Part 1 of 5). This article focuses on getting the project to build successfully, both for the current state of the code and the 4-year-old initial version of the code.
Where to start?
Understand makes it easy to know where to start looking to track down a bug, Find where to place breakpoints, and identify which locations in the code need to be updated.
Measuring Your Code
Learn about the available metrics in Understand, the ways to explore them, and how they can help you solve problems.
Functions Shall Be lowerCamelCase
Fixing function names with Understand’s Rename Refactor tool, and some recent improvements to it
Git Comparison Projects
You can now create Understand Comparison Projects directly from git
Click Bait
A behind the scenes view of the SciTool’s Blog
Debugging Understand with Understand
Tracking down an issue with nested typedef structs in the Data Members graph using Understand.