Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 98841 - Last Review: January 9, 2006 - Revision: 4.0
ANSI C specifies the requirements for a "strictly conforming" program
This article was previously published under Q98841
Note Microsoft Visual C++ .NET 2002 and Microsoft Visual C++ .NET 2003 support both the managed code model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows code model. The information in this article applies only to unmanaged Visual C++ code. Microsoft Visual C++ 2005 supports both the managed code
model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows
code model.
Names starting with a single underscore and an uppercase
letter, or names beginning with a double underscore and a lowercase letter, can
be used in a "conforming" C program translated by a "conforming"
implementation; these names, and the meaning and syntax associated with each
name, are reserved by the implementation. ANSI C also specifies the
requirements for a "strictly conforming" program, in which these constructions
are not permitted.
Other compilers may ignore such names that exist in the
implementation space, or produce any desired behavior, and the program can
still be defined as conforming.
The Microsoft C compiler does not
have a strictly conforming mode of operation. As a result, if a developer uses
another vendor's compiler, which is a strictly conforming implementation, the
Microsoft headers will not work. In this case, the vendor of the strictly
conforming compiler must provide the appropriate headers for the system.
Because the standard headers are part of the implementation, there
is no requirement for the header mechanisms provided by one implementation to
be interoperable with the mechanisms of another. Another implementation MUST
provide its own compatible set of standard headers and their associated
inclusion mechanisms.
APPLIES TO
- Microsoft C/C++ Professional Development System 7.0
- Microsoft Visual C++ 1.0 Professional Edition
- Microsoft Visual C++ 1.5 Professional Edition
- Microsoft Visual C++ 1.51
- Microsoft Visual C++ 1.52 Professional Edition
- Microsoft Visual C++ 2.0 Professional Edition
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++, 32-bit Learning Edition 6.0
- Microsoft Visual C++ 2005 Express Edition
- Microsoft Visual C++ .NET 2003 Standard Edition
- Microsoft Visual C++ .NET 2002 Standard Edition
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate