We're glad to offer to your attention a quick overview of the PVS-Studio 7.05 code analyzer release. The analyzer is enriched with twenty new diagnostics and infrastructure improvements.
For a long time, we've been trying to stick to the following release schedule: once every two months. Now the release has been delayed, which we ourselves did not like. Four months is too long. First, it turned out that during this time the system of release automatic preparation magically broke down, and we had to repair it. Secondly, we've got a request from one of our users who was worried why there was no release for so long and how things were actually going with the analyzer. One shouldn't make customers and users worry.
The reason for the delay was various conferences that came together in October, November and went one by one. Preparation to talks and trips to conferences with booths required a lot of time from many employees. We took part in such conferences, as Stachka, C++Russia, Joker, DotNext, Dump, Highload++, SQA Days, SECR, DevGamm, CLRium, CoreHard. And at the same time, as for PVS-Studio, we wanted to get this, that and the third done... This is a wrong approach and we shouldn't have postponed the release, but ended it up with fewer number of refinements. We'll take it into account and do our best to stick to two-month delivery schedule.
Now about the most important improvements:
- The Blame Notifier utility meant to notify developers about the analysis results is now available on all platforms supported by the analyzer (Windows, Linux, macOS). Blame Notifier uses the information from the version control system (SVN, Git, Mercurial) to identify the person who wrote the code that triggered an analyzer warning.
- We added support for .NET Core 3 and 3.1 projects to the C# analyzer.
- In the Windows analyzer version, it is now possible to set directories excluded from the analysis at the level of a certain Visual Studio project or solution using .pvsconfig files.
- 20 new diagnostics have been implemented. The list of them is available on the release history page. This time, the most interesting should be the V1044 diagnostic.
You're welcome to download and try the new PVS-Studio analyzer version. For those who are mildly acquainted with the topic of code analysis, we suggest that you read a quick overview of our analyzer: "A brief overview of the PVS-Studio static code analyzer". We hope you'll be interested in the methodology of static code analysis and you'll want to use it in order to improve your development process.