This section lists MIDL compiler error and warning messages.
An error or warning message sometimes specifies the name of one or more MIDL compiler mode switches. The MIDL compiler accepts an IDL file when you use some mode switches but generates errors for the same file when you do not use mode switches. For example, you can include certain ACF attributes in an IDL file when you use the /app_config switch, but that IDL file will generate an error if you compile without using the /app_config switch.
Command-line errors appear in the following format:
Command line error : MIDLnnnn : <error text>
[<additional error information>]
The additional-error information field provides context-specific information about the error. The information in this field depends on the error message. For example, when an unresolved type-declaration error occurs, the additional-information field displays the name of the type that could not be resolved.
Compile-time warnings appear in the following format:
<FileName>(line#) : warning MIDLnnnn :
<warning text>
[optional context information] :
Compile-time errors appear in the following format:
<FileName>(line#) : error MIDLnnnn :
<error text>
[optional context information] :
Optional context information refers to the context in which the error occurred. The MIDL compiler reports this information to help you quickly find the error in the IDL file. Context information is generated when the MIDL compiler discovers an error during semantic analysis of type and procedure signatures.
System error messages appear in the following format:
<FileName>(line#) : MIDL error 0xnnnn :
"Unexpected internal compiler problem. Try to find a workaround."
The absence of relevant context information is not intended to make your life more difficult. This message is generated by an error that was, quite literally, unexpected. The hexadecimal error number is a Windows NT or Windows 9x system error identifier. You may find additional information regarding your particular error in the WINERROR.H or.NTSTATUS.H files. For more information on working around the conditions that caused this error, see the error text for compiler error MIDL9008.