Xref: news2.mv.net comp.os.msdos.djgpp:3306
From: tward AT wybbs DOT wynalda DOT com (Thad Ward)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gcc messages > file
Date: Wed, 01 May 1996 09:01:11 GMT
Organization: CompuServe Incorporated
Lines: 19
Message-ID: <31872839.914281@news.compuserve.com>
References: <Pine DOT VUL DOT 3 DOT 91 DOT 960415123808 DOT 14476F-100000 AT zeus DOT adv-boeblingen DOT de> <317258AF DOT 61C1 AT Mathematik DOT tu-chemnitz DOT de> <4lclse$d2c AT yama DOT mcc DOT ac DOT uk> <4livp3$892 AT trog DOT dra DOT hmg DOT gb>
NNTP-Posting-Host: ad39-130.compuserve.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On 23 Apr 1996 16:16:35 GMT, itmiller AT taz DOT dra DOT hmg DOT gb (Ian Miller)
wrote:

>
>In article <4lclse$d2c AT yama DOT mcc DOT ac DOT uk>, tpj AT sn2 DOT ee DOT umist DOT ac DOT uk (TPJ Mc Guigan) writes:
>|>
>|>Hmmm, what about redirecting stderr via "gcc file.c >& err.msg"? Don't know
>|>if this type of arrangement is what you want. Just in case it is ---
>|>
>|>  >   redirects stdout
>|>  >&  redirects stderr and stdout
>|>  >&> redirects stderr
>
>In DOS?

in 4DOS

---
Thad Ward