So don't be surprised if the analyzer starts issuing many warnings for that code which used to seem correct for the analyzer. For example, now the analyzer performs a double loop passage, which allows it to define the range of possible values of variables, changing in a loop, more accurately. The variable is assigned but is not used until the end of the function.Ī much more interesting feature is that a mechanism of virtual values was significantly redesigned in the kernel of C++ analyzer. The initial value of the index in the nested loop equals 'i'. The variable is assigned but is not used until the end of the function. The variable can be constructed in a lower level scope. Several new diagnostics were added, but nothing remarkable: More details are given in the article " PVS-Studio's incremental analysis mode". Thus, more options of performing the analysis become available that will let you configure the analyzer in terms of the needs of the project. The usage of this mode will let "accumulate" information about the files that need to be analyzed. In the command line module PVS-Studio_Cmd.exe a new incremental analysis mode "AppendScan" was added. More detailed information can be received from the documentation sections " Integration of PVS-Studio analysis results into SonarQube" and " How to run PVS-Studio on Linux". The next step was the implementation of a plugin for SonarQube quality control system and adding a mode of mass warnings suppression for Linux. ![]() In other words, the Linux version is overtaking Windows version of analyzer on its abilities. ![]() We continue to develop our analyzer in relation to Linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |