C++ tutorials, C and C++ news, and information about Visual Studio, Visual Studio Code, and Vcpkg from the Microsoft C++ team.
March 30, 2020Mar 30, 202003/30/20One of the new features of Visual Studio 2019 (beginning with version 16.4) and .NET Core 3.1 is the ability to build C++/CLI projects targeting .NET Core. This can be done either directly with cl.exe and link.exe (using the new /clr:netcore option) or via MSBuild (using <CLRSupport>NetCore</CLRSupport>).
March 27, 2020Mar 27, 202003/27/20We are excited to announce full support for a conformant preprocessor in the MSVC toolset starting with Visual Studio 2019 version 16.6 Preview 2.
Since the original blog post announcing preprocessor conformance changes, we’ve come a long way and are now ready to announce the completion of the C/C++ conformant preprocessor and its move to a non-experimental,
March 26, 2020Mar 26, 202003/26/20Whether you’re using Doxygen or XML Doc Comments, Visual Studio version 16.6 Preview 2 provides automatic comment stub generation as well as Quick Info, Parameter Help, and Member List tooltip support.
Stub Generation
By default, the stub generation is set to XML Doc Comments.
March 26, 2020Mar 26, 202003/26/20 Introducing the IntelliSense Code Linter for C++; a preview of "as-you-type" code analysis with fixups. Try it out today in Visual Studio 2019 16.6 Preview 2.
March 13, 2020Mar 13, 202003/13/20In a previous blog post, Microsoft described the Spectre mitigations available under /Qspectre. These mitigations, while not significantly impacting performance, do not protect against all possible speculative load attacks, described in industry research as Load Value Injection. We are now adding two new switches /Qspectre-load and /Qspectre-load-cf to provide a more complete mitigation of Spectre attacks based on loads for customers.
March 6, 2020Mar 6, 202003/6/20We’re happy to announce today the release of the C++ Build Insights SDK, a framework that gives you access to MSVC build time information via C and C++ APIs. To accompany this release, we are making vcperf open source on GitHub.
March 2, 2020Mar 2, 202003/2/20The final specifier in C++ marks a class or virtual member function as one which cannot be derived from or overriden. For example, consider the following code:
1 2 3 4 5 6 7 | struct base { virtual void f() const = 0; }; struct derived final : base { void f() const override {} }; |
If we attempt to write a new class which derives from derived then we get a compiler error:
1 2 | struct oh_no : derived { }; |
1 2 | <source>(9): error C3246: 'oh_no': cannot inherit from 'derived' as it has been declared as 'final' <source>(5): note: see declaration of 'derived' |
The final specifier is useful for expressing to readers of the code that a class is not to be derived from and having the compiler enforce this,
