This is a continuation of a small note series about regular checks of the Blender project with the PVS-Studio static analyzer. The aim of these publications is to demonstrate how it is beneficial to use static code analysis tools regularly. In doing so, many errors can be found at the earliest stage, and fixing them will be cheap and fast. 🔗 https://karpov2007.medium.com/blender-and-a-null-pointer-fdce436641e2

New #UE4 blog post by Coconut Lizard! This time, taking a look
Unreal Engine's Sequencer code, using PVS-Studio 🔗https://www.coconutlizard.co.uk/blog/TheConsequenceOfTheMissingReferences/

Example of How New Diagnostics Appear in PVS-Studio https://www.viva64.com/en/b/0814/

One Useful Comment https://www.viva64.com/en/b/0815/

PVS-Studio Analyzer Is Now in the Russian Software Registry https://www.viva64.com/en/b/0816/

How PVS-Studio Prevents Rash Code Changes https://www.viva64.com/en/b/0817/

📻 We're happy to share an episode of our friends, The Complete Developer Podcast.

The guest of the show was our C++ developer, Yuri Minaev. 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.
Visit the link to learn more about what it takes to develop a static code analyzer 👇

https://completedeveloperpodcast.com/metacoding-coding-code-analyzers/

MacOS Kernel, Is This Apple Rotten? https://www.viva64.com/en/b/0818/

PVS-Studio Team's Kanban Board. Part 1: Agile https://www.viva64.com/en/b/0819/

Rob and Jason are joined by Ben Craig. They first discuss blog posts detailing how function call resolution works in C++ and algorithm selection. Then they talk to Ben Craig about his efforts with the C++ Freestanding proposal, what progress has been made, what still needs to be done, and more.
🔗https://cppcast.com/freestanding-update/

In late 2007, Aaron Sanders, one of the first followers of Kanban, wrote on the Kanbandev mailing list that the team he worked with spent 90% of the available productivity on bug fixes.
How does it relate to static analysis? 🤔 Visit the link to learn.
https://karpov2007.medium.com/life-before-and-after-pvs-studio-6c2cae3530f7

👨‍💻 As you know, our clients are developers. Sometimes developers can surprise you.
For example, one of our users wrote his own script. It allows configuring emails about errors found by PVS-Studio. The difference between this script and our blame-notifier is that it does not require .NET Core on Linux.
📝We decided to write a short note about this Perl script, because we believe that it can be useful to someone. https://pvs-studio.com/en/b/0821/

Rob and Jason are joined by Nikolai Wuttke. They first discuss a blog post series from Raymond Chen on coroutines and the upcoming pure virtual C++ conference. Then they talk to Nikolai Wuttke about Rigel Engine, a modern C++ reimplementation of Duke Nukem II.
https://cppcast.com/rigel-engine/

🔸Static analysis is better than dynamic?
🔸Too expensive?
🔸Too hard to use?

It's time to dispel these and other myths we often hear about static analysis.

Feel free to join our channel to learn more about these noisy helpers 📣https://www.youtube.com/watch?v=PXF8fRUTA_U

Rob and Jason are joined by David Millington, an Australian developer from Embarcadero.
🔗 https://cppcast.com/cpp-builder/

Finally! PVS-Studio Supports .NET 5 Projects https://pvs-studio.com/en/b/0822/

Roslyn API: Why PVS-Studio Was Analyzing the Project So Long https://pvs-studio.com/en/b/0823/

🎉Wow, the first episode of the Cherno Podcast with our C++ developer as a guest! Feel free to check it 👇https://www.youtube.com/watch?v=ikjh2hvJ-f0

''Static code analyzer'' sounds a bit complicated, doesn't it? What if after reading this small note, you will have enough knowledge to create your own static analyzer? Interested? Let's get started! https://www.codingvila.com/2021/03/create-static-code-analyzer.html