Breaking Changes in the Visual C++ Compiler
Visual Studio .NET 2003
The Visual C++ compiler has significantly increased its conformance with the C++ standard in the Visual Studio .NET 2003 release. With this conformance comes a number of breaking changes. Many of those changes now result in compiler errors, where no compiler errors were given in previous releases. However, there are also a number of silent, or runtime errors, which are described in this section.
A nonconformance related breaking change is that just-in time debugging for Managed Extensions for C++ images will not work unless you either add DebuggableAttribute or use a configuration file; see Making an Image Easier to Debug for more information.
For remaining conformance issues, see Standard Compliance Issues in Visual C++.
- Throwing New Behavior Changed
- String Literals Have Proper Type of const char[]
- Overloading of Function Templates
- Argument Dependent (Koenig) Lookup Now Supported
- Zero Initialization of POD and Scalar Types
- Old-Style Name Mangling for Exported Template Instantiations
- Summary of Compile-Time Breaking Changes
