Metacoding: Coding Code Analyzers

Static code analysis automatically examines source code before it compiles or is run. It does this by comparing the code code to a set of rules or standards. This process allows for the automation of code reviews and can be used in conjunction with peer reviews.

Yuri Minaev is C++ developer working for the PVS-Studio company as one of developers of the code analyzer for C++. His primary responsibility is to keep low-level stuff in order and add new features to the core module. Yuri has been developing software for over 12 years and with PVS-Studio for two years. When not coding, he periodically gives talks at various conferences – mainly on topics related to static analysis and C++.

PVS-Studio analyzes code designed for 32-bit and 64-bit systems as well as embedded ARM platforms. It is cross platform, working on Windows, Linux and MacOS 64-bit environments. Use it to generate reports that help you find and fix bugs before they become a problem.

Thank you Yuri for joining us again and getting even deeper into what it takes to develop a static code analyzer. Code analysis allows developers to keep their codebase clean and detect problems before they occur. This allows developers to not worry about simple things and focus on higher level concerns. The process to take away these concerns is anything but simple. Building and maintaining a static code analyzer takes a lot of work. Even if you aren’t interested in building or working on one, understanding the process that goes into building such complex solutions will help you in your career.

Tricks of the Trade

Use automated checks on your stuff so you don’t have to be smart.

Editor’s Notes:

Tagged with: , , ,