ANSI C specifies the requirements for a "strictly conforming" program (98841)



The information in this article applies to:

  • Microsoft C/C++ for MS-DOS 7.0
  • Microsoft Visual C++ 1.0
  • Microsoft Visual C++ 1.5
  • Microsoft Visual C++ 1.51
  • Microsoft Visual C++ 1.52
  • Microsoft Visual C++ 2.0
  • Microsoft Visual C++ 4.0
  • Microsoft Visual C++, 32-bit Enterprise Edition 5.0
  • Microsoft Visual C++, 32-bit Enterprise Edition 6.0
  • Microsoft Visual C++, 32-bit Professional Edition 5.0
  • Microsoft Visual C++, 32-bit Professional Edition 6.0
  • Microsoft Visual C++, 32-bit Learning Edition 6.0
  • Microsoft Visual C++ 2005 Express Edition
  • Microsoft Visual C++ .NET (2003)
  • Microsoft Visual C++ .NET (2002)

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.

SUMMARY

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.

MORE INFORMATION

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.

Modification Type:MajorLast Reviewed:1/9/2006
Keywords:kbinfo kbLangC KB98841 kbAudDeveloper