3 ms·

> If they're not building with -Wall -Wextra -Werror, are they really going to make use of PVS-Studio's output? This is very likely. Do not forget that the sta

> If they're not building with -Wall -Wextra -Werror, are they really going to make use of PVS-Studio's output? This is very likely. Do not forget that the static analyzer is not just a warning. This is also the infrastructure. For example, PVS-Studio is: - Saving and loading analysis results allow doing overnight checks - during the night the analyzer does the scanning and provides you with the results in the morning. - Interactive filtering of the analysis results (the log file) in the PVS-Studio window: by the diagnostic number, file name, the keyword in the text of the diagnostic. - BlameNotifier utility. The tool allows you to send e-mail notifications to the developers about bugs that PVS-Studio found during a night run. - Mass Suppression - ability to suppress all old messages raised for the legacy code, so that the analyzer reports 0 warnings. You can always go back to the suppressed messages later. This feature allows you to seamlessly integrate PVS-Studio into your development process and focus on errors found in new code only. Details: https://www.viva64.com/en/m/0032/ https://www.viva64.com/en/m/0032/ - Relative paths in report files to view them on different machines. - CLMonitoring feature allows analyzing the projects that have no Visual Studio files (.sln/.vcxproj); in case the CLMonitoring functionality is not enough, there is a possibility to integrate PVS-Studio in a Makefile-based build system manually. - pvs-studio-analyzer - a utility similar to CLMonitoring, but working under Linux. - Possibility to exclude files from the analysis by name, folder or mask; to run the analysis on the files modified during the last N days. - Integration with SonarQube. It is an open source platform, designed for continuous analysis and measurement of code quality. - and so on

virtualized 9y ago
I don't remember reading about any of that even though I am a regular reader of your "checked projects" series. All of the relevant information on your web site is hidden in some wall of text. Please consider hiring someone who knows how to sell something.
- JdeBP 9y ago
  It isn't hidden, really. I followed the hyperlink at the top to the main page of the site, and the bullet-point list that you are responding to is right there, on that very first page. It is under a heading entitled Main Features of PVS-Studio. * https://www.viva64.com/en/pvs-studio/ https://www.viva64.com/en/pvs-studio/
  - virtualized 9y ago
    "Main Features of PVS-Studio" is one of those walls of text that I meant.
geofft 9y ago
Suppressing old errors is definitely useful. Most of the other things sound like tools to fix erroneous code after it's landed. If you're using -Werror, and you have something that makes sure the code builds before merging it to master / trunk, you can't commit erroneous code in the first place.

virtualized 9y ago

I don't remember reading about any of that even though I am a regular reader of your "checked projects" series. All of the relevant information on your web site is hidden in some wall of text. Please consider hiring someone who knows how to sell something.

JdeBP 9y ago
It isn't hidden, really. I followed the hyperlink at the top to the main page of the site, and the bullet-point list that you are responding to is right there, on that very first page. It is under a heading entitled Main Features of PVS-Studio. * https://www.viva64.com/en/pvs-studio/ https://www.viva64.com/en/pvs-studio/
- virtualized 9y ago
  "Main Features of PVS-Studio" is one of those walls of text that I meant.

geofft 9y ago

Suppressing old errors is definitely useful. Most of the other things sound like tools to fix erroneous code after it's landed. If you're using -Werror, and you have something that makes sure the code builds before merging it to master / trunk, you can't commit erroneous code in the first place.