Description Maxime Daniel 2005-06-06 07:03:12 EDT

Investigating why the BathCompilerTest series of tests printed to the console
whereas the instance of batch compiler used specifically uses non default output
streams, it appeared that the delegate compiler used by the batch compiler does
post verbose information messages to the System.out stream (instead of posting
them to the specified output file).

In order to avoid polluting the console, a quick fix is attached that disables
the batch compiler tests that use the -verbose option. A better fix would be to
 propagate the logger initialized by the batch compiler into the delegate
compiler so that the latter could report verbose messages through the logger.

The alternative path that would augment the responsibilities of the
ICompilerRequestor to cope with real time informative messages seems less
appropriate (real time error messages not being the main focus of a compilation
result, the object that is passed back to the requestor.) 
A third approach would imitate more closely the behavior of a command line
compiler and would consider redirecting System.out itself to a file. In that
case, though, Main should be amended so that its constructors would no more take
parameters for err and out output streams. (In other words, either we consider
that Main should be able to take alternate streams parameters at construction
time and it should then *always* use them, or we consider that Main *always*
operates upon standard out and err, and BatchCompilerTest must provide for
System.out and System.err redirection. While changing System.out itself is not
an option, preventing it to write to the console might be one.)

The first option seems to be the cleaner path (IMHO), assuming then that command
line instances of the batch compiler would merely pass System.out and System.err
down the chain.