-WmsgFb (-WmsgFbi, -WmsgFbm): Set Message File Format for Batch Mode

MESSAGES

Compilation Unit

  -WmsgFb[v|m] 
  

v: Verbose format

m: Microsoft format

  -WmsgFbm 
  

None

None

You can start the Compiler with additional arguments (e.g., files to be compiled together with Compiler options). If the Compiler has been started with arguments (e.g., from the Make Tool or with the appropriate argument from an external editor), the Compiler compiles the files in a batch mode. No Compiler window is visible and the Compiler terminates after job completion.

If the Compiler is in batch mode, the Compiler messages are written to a file instead of to the screen. This file contains only the compiler messages (see the examples in Listing: Message file formats (batch mode)).

The Compiler uses a Microsoft message format to write the Compiler messages (errors, warnings, information messages) if the compiler is in batch mode.

This option changes the default format from the Microsoft format (only line information) to a more verbose error format with line, column, and source information.

See the following listing for examples showing the differing message formats.

void foo(void) { 
 int i, j; 
 for (i=0;i<1;i++); 
} 
The Compiler may produce the following file if it is running in batch mode (e.g., started from the Make tool): 
X:\C.C(3): INFORMATION C2901: Unrolling loop 
X:\C.C(2): INFORMATION C5702: j: declared in function foo but not referenced 
Setting the format to verbose, more information is stored in the file: 
-WmsgFbv 
>> in "X:\C.C", line 3, col 2, pos 33 
 int i, j; 
 for (i=0;i<1;i++); 
 ^ 
INFORMATION C2901: Unrolling loop 
>> in "X:\C.C", line 2, col 10, pos 28 
void foo(void) { 
 int i, j; 
 ^ 
INFORMATION C5702: j: declared in function foo but not referenced 

ERRORFILE: Error filename Specification environment variable

-WmsgFi (-WmsgFiv, -WmsgFim): Set Message Format for Interactive Mode