Примеры использования Incremental analysis на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
So you are welcome to try the incremental analysis.
To sum it up: incremental analysis is surely a must-try.
This setting allows setting a time limit, after which the incremental analysis files will be aborted.
Incremental analysis mode is designed to solve the second problem.
For regular use, you can set up incremental analysis on every developer's machine;
Incremental analysis supports the base of"uninteresting" messages.
To learn more about PVS-Studio's incremental analysis, see the article" PVS-Studio's incremental analysis mode.
However, we still recommend that developers first of all use PVS-Studio on their local machines in the incremental analysis mode.
To sum it up: Incremental analysis is the feature you obviously ought to try.
If necessary, you can also enter an intermediate phase,which will run between the two described- incremental analysis on the build server.
You can use incremental analysis to check freshly modified files.
Therefore, we do recommend you to use PVS-Studio both for daily runs on the server and in the incremental analysis mode on the programmers' computers.
After the build, the incremental analysis starts automatically in the background mode.
If you do need to use it in this way and your project is builtwith MSBuild build system, use the incremental analysis mode of command line module'PVS-Studio_Cmd. exe.
So the incremental analysis will be automatically provided by using the independent command line version.
To determine the modified filesin the C/C++ projects, which require incremental analysis, the analyzer uses MSBuild tools to work with the file tracking logs*. tlog files.
The incremental analysis mode for Visual Studio solutions is also available in the command line module PVS-Studio_Cmd. exe.
The arguments of the command line module(PVS-Studio_Cmd. exe)to start the incremental analysis are given in the section" Analyzing Visual C++(. vcxproj) and Visual C(. csproj) projects from the command line.
The incremental analysis mode allows fixing errors right after they have been made, even before they get into the control version system.
The users who are familiar with PVS-Studio incremental analysis mode within the IDE naturally will miss this feature in the command line mode.
Incremental analysis in PVS-Studio 4.30- The ability to run the analyzer automatically for files that have just been edited or recompiled.
If one used it regularly(see incremental analysis), an error like the described one and perhaps many of plainer bugs would have never occurred.
PVS-Studio's incremental analysis mode allows you to check only those files that have been modified/affected since the last build.
You can turn on the afterbuild incremental analysis in the PVS-Studio menu:"PVS-Studio-> Analysis after Build(Modified Files Only)" Figure 1.
The incremental analysis mode that implements the approaches similar to the approaches of MSBuild for the incremental build, allows to solve this problem.
If PVS-Studio detects such modifications, incremental analysis will be launched automatically, and an animated PVS-Studio icon will appear in the notification area Figure 2.
For this phase, incremental analysis is ideal, which enables to analyze the code the developer is working with.
This is because we use incremental analysis that helps us fix detected errors long before the code gets into the version control system.
The main task, solved when using incremental analysis is the analyzer run automation on the developer's machine immediately after the code is compiled.
We recommend using the incremental analysis mode, which allows you to have analysis automatically initiated only for recently modified code after the build.