Mail Archives: djgpp/1998/02/14/16:48:46
From: | ram AT tiac DOT net (robert a. moeser)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | saving error messages
|
Date: | Sat, 14 Feb 1998 16:31:40 -0500
|
Organization: | disorganized
|
Lines: | 21
|
Message-ID: | <ram-1402981631400001@news.tiac.net>
|
NNTP-Posting-Host: | ram.tiac.net
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
hi!
i don't make any mistakes when i write programs (!) so i
never had to actually read any compiler error messages...
but my students do (so far), and sometimes there are so many
that that first critical message scrolls off to the bit bucket.
i tried re-directing the error output of gcc, but it must be
going around stdout or whatever.
i'll keep poking around, but i hope this is an easy one:
can gcc be told to stop after one error? OR
can the error output of gcc be somehow directed to a file
for calm perusal after the dust settles?
thanks.
-- rob
- Raw text -