PVS-Studio 7.08

PVS-Studio is the analyzer that searches for bugs in programs written in C, C++, C#, and Java. The PVS-Studio 7.08 release includes a lot of new exciting features. The C# analyzer, in addition to working on the Windows OS, now also works on Linux and macOS....

PVS-Studio is the analyzer that searches for bugs in programs written in C, C++, C#, and Java. The PVS-Studio 7.08 release includes a lot of new exciting features. The C## analyzer, in addition to working on the Windows OS, now also works on Linux and macOS. It is now possible to output analysis results in the TeamCity format. The Perforce system is supported in the utility for automatic notification of developers. The plugin for the JetBrains Rider development environment is now available. In the PVS-Studio Java analyzer, you can search for Java SE API compatibility problems. Let's look at these new features in more detail in the article.

C## analyzer for Linux and macOS

At the end of April, we started beta testing of the C## analyzer for Linux and macOS. It was quite successful: we collected feedback, made a number of improvements and fixes.

Now finally, we are releasing the analyzer version comprising the C## analyzer for Linux and macOS! Thus, now the C## analyzer, as well as C, C++, and Java analyzers, is available under all platforms supported by PVS-Studio - Windows, Linux, and macOS.

The command-line utility for analyzing C## projects under Linux \ macOS is called pvs-studio-dotnet. The features of installing and using the analyzer are described in the corresponding sections of the documentation:

• analyzer installation;
• analyzer usage;

PVS-Studio plugin for the JetBrains Rider IDE

On the sidelines of the development and testing of the C## analyzer for Linux and macOS, we have also been developing the PVS-Studio plugin for JetBrains Rider. A no less positive news is that it's also included in the release and is available under all supported platforms: Windows, Linux, macOS.

For more information about installing and using the plugin, see the documentation section "Using PVS-Studio with JetBrains Rider".

New analysis mode of pull requests \ merge requests \ commits

In the Windows version of the analyzer, in the PVS-Studio_Cmd command line utility, a new mode of checking the specified list of files has been added, which is useful for setting up automatic checking of pull \ merge requests and commits.

Despite the fact that previous analyzer versions already had a similar mode, working with it wasn't the most convenient, especially for C++ projects.

Firstly, in the case of analyzing both C++ and C## projects, an XML file was required to specify the list of files for analysis (via the --sourceFiles flag). In other words, it had to be formed in a special way from the list of files in PR, MR, and a commit. This adds an additional step.

Secondly, let's say source files had to be analyzed based on .h files. That is the .h file is changed, you need to analyze all files where it was included explicitly or indirectly. Previously the presence of build system artifacts (tlog files) was required. In addition, one had to first get these files when building the project being checked.

Now it is much easier and more convenient to use this mode – you don't need any tlog files or special XML files. One can simply use the same --sourceFiles flag to send a simple text file with a list of files for analysis. That's it, no tlog files! To solve the problem of storing dependencies, the analyzer now creates a special cache of dependencies between the header and source files, instead of using tlog files, which greatly simplifies this mode of use.

This mode is described in more detail in the section "Setting individual files for checking" in the documentation section "Analyzing Visual Studio / MSBuild / .NET Core projects from the command line using PVS-Studio".

Other improvements and additions

• The PVS-Studio_Cmd and pvs-studio-dotnet utilities now allow you to pass. pvsconfig files via command-line arguments (--rulesConfig (-C)).
• Output format for TeamCity was added in a plog-converter - a utility for converting logs on Linux and macOS. In the last release, this output format was added in the PlogConverter for Windows.
• We have annotated a lot of methods from the Unity libraries, which will allow the C## analyzer to have more information about these methods, and as a result – to conduct more accurate analysis of Unity projects.
• The blame-notifier utility for automatic developers notification now supports yet another version control system - Perforce. Thus, now the blame-notifier can work with the following VCS: Git, SVN, Mercurial, and Perforce. In addition, it can now automatically get a list of report recipients for Perforce.
• In Unreal Engine 4.25, it is now possible to use various groups of PVS-Studio diagnostic rules (previously, only the "General Analysis" group was available). For information on how to enable various groups of diagnostics, see the corresponding section of the documentation.

visual studio code visual studio code

💲 Live CollabPlay: https://youtu.be/B6LCFSPdsE0 💲 Hospedagem com Desconto Exclusivo: https://tekers.tech/4e587 Não é todo programador que gosta de compartilh...

#vscode Hello, my friends and fellow developers, this video is all about User Snippets. That means the Snippets (Code Shortcuts) that you can make for yourse...

We are pleased to announce that the July release of the Python extension is now available for Visual Studio Code. You can download the Python extension from the Marketplace, or install it directly from the extension gallery in Visual Studio Code. If you already have the Python extension installed, you can also get the latest update by restarting Visual Studio Code. You can read more about Python support in Visual Studio Code in the documentation .

If you’re looking for a fast and lightweight open-source code editor, Visual Studio Code has you covered. Come for a deep dive into the features of Visual Studio Code which provide a rich, productive environment for C++ development.

We speak to the creator of Visual Studio Code about the early challenges to now becoming the most popular development environment in the world.