MIDL compiler error and warning messages

powerbuilder

<>This section lists MIDL compiler error and warning messages.</P>
" f1 ^0 d' ]- I. R, A' q" u# L<>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 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.
3 V. V+ j' Z; T/ uCommand-line errors appear in the following format:</P>
$ n4 C0 ]3 G1 x1 ?<>Command line error : MIDLnnnn : &lt;error text&gt;
% l2 {1 [$ r5 z  j% m) a% a1 U. o[&lt;additional error information&gt;]
+ R5 a. d2 D; V </P>
# E% ^4 a7 d# m7 f: x7 h2 F9 L  m<>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:</P>
# W5 V4 m& t% E, v8 l8 o<>&lt;FileName&gt;(line#) : warning MIDLnnnn :  
&lt;warning text&gt;
2 V! N1 \9 t: q! [6 k[optional context information] :
+ [. T) g9 |9 m, G$ C </P>
4 g. r, B) ~9 ^' @; ?<>Compile-time errors appear in the following format:</P>
<>&lt;FileName&gt;(line#) : error MIDLnnnn :  
&lt;error text&gt;
[optional context information] :
( @% O/ c7 {0 r! b </P>
1 i! W# a& c- Q( O7 ^' I' N<>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.</P>
<>MIDL1000 : missing source file name</P>
$ a9 Y( c8 b$ D2 s; i0 V4 h5 y) {<>No input file has been specified in the MIDL compiler command line.</P>
1 I! T4 v$ q, y% ^<>MIDL1001 : cannot open input file</P>
2 `; q" h6 ~; i1 r. y/ z<>The input file specified could not be opened.</P>
<>MIDL1002 : error while reading input file</P>
! _$ J( o, y1 w9 ^* y& e. A<>The system returned an error while reading the input file.</P>
<>MIDL1003 : error returned by the C preprocessor</P>
<>The preprocessor returned an error. The error message is directed to the output stream.</P>
<>MIDL1004 : cannot execute C preprocessor</P>
! Q. p5 F; `) J# |% A  v<>The operating system reported an error when it tried to spawn the preprocessor. With MS-DOS, this error can occur when the argument list exceeds 128 bytes. You can reduce the size of the argument list by using a response file.</P>
<>MIDL1005 : cannot find C preprocessor</P>
<>The MIDL compiler cannot locate the preprocessor in the specified path or in the path specified by the PATH environment variable.</P>
<>MIDL1006 : invalid C preprocessor executable</P>
5 y" Y% Y1 A& u" V, }- Y0 Y, E<>The specified preprocessor is not executable or has an invalid executable-file format.</P>
3 a  E$ o* g  @5 Y# n' \; L<>MIDL1007 : switch specified more than once on command line</P>
<>A switch has been redefined. The redefined switch is displayed after the error message.</P>