Date: Mon, 15 Apr 1996 08:43:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA>
Cc: djgpp AT delorie DOT com
Subject: Re: Error messages and warnings...
In-Reply-To: <4kqb0s$m28@freenet-news.carleton.ca>
Message-Id: <Pine.SUN.3.91.960415083521.3742K-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 14 Apr 1996, Paul Derbyshire wrote:

> 
> Tom Sgouros (tomss AT ids DOT net) writes:
> > Can anyone tell me how to record the voluminous error messages that the
> > code I am working on generates? (I am porting a big program that was
> 
> You can redirect stderr to a file with an obscure go32 option listed in
> the FAQ somewhere, but it has a side effect: once in a while the error
> messages thus redirected end up in the .a files and other files generated
> along the compile, assemble, link chain! These of course completely mess

That is old news.  Even in DJGPP v1.x the problem with feeding error
messages of cpp to the compiler as result of redirection was cured long
ago; in DJGPP v2 it never existed.  So now you can use the redirection
without fear.  DJGPP v2 doesn't use the GO32 environment variable at all,
but it brings a little wonder called `redir' to handle such redirection. 
Look it up in your on-line docs. 

> As a result this redirection is not that great, and I know of no
> alternative that works perfectly.

The best alternative I know is to compile from an editor that catches the
error messages in a buffer (by properly redirecting stderr, or by
installing a handler for DOS output functions).  You can then do whatever 
you like with those mesages, like save them into a file, print them, feed 
them to your favorite tax-calculating program, etc.