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
Category: Developer Notes
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.
Functions Shall Be lowerCamelCase
Fixing function names with Understand’s Rename Refactor tool, and some recent improvements to it
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.
As-Built Documentation
What does “as-built documentation” mean? For me, it means being able to find answers to my questions by quickly viewing references in the code. Take a look at how I use as-built documentation in a real-life scenario with Understand.
Getting Git: Walking File History
Join me in a trip down the rabbit hole of making a “File History Diff Walker.”
Getting Git: Blame
Natasha explores the origin of the Blame margin in Understand.
Getting Git: Submodules
How we will be improving git submodule support in Understand.