Subject:
|
RE: MPD Builder
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 16 Feb 1999 23:28:04 GMT
|
Viewed:
|
684 times
|
| |
|
|
Some of the Windows compilers come with a program called RSE that redirects
stderr to stdout.
Under Windows NT you can do something like
prog > output 2>&1
which redirects stdout to 'output' and redirect handle number 2 (stderr)
into handle number 1 (stdout).
You can also do
prog 2> out.stderr 1> out.stdout
to get them to go to different places. This works under cmd.exe. Your
mileage may vary with other shells (I use the Hamilton C-Shell).
---
Dave Hylands Email: DHylands@creo.com 3700 Gilmore Way
Principal Software Developer Tel: (604) 451-2700 x2329 Burnaby B.C.
Creo Products Inc. Fax: (604) 437-9891 Canada V5G 4M1
-----Original Message-----
From: blisses@worldnet.att.net [mailto:blisses@worldnet.att.net]
Sent: Tuesday, February 16, 1999 5:54 AM
To: lugnet.cad@lugnet.com
Subject: Re: MPD Builder
On Tue, 16 Feb 1999 08:49:50 GMT, sparre@sys-323.risoe.dk (Jacob Sparre
Andersen) wrote:
> Steve Bliss (blisses@worldnet.att.net) wrote:
> > Actually, one anomoly I noticed is that the processing messages aren't
> > written to stdout. I couldn't pipe them to a file. I don't know if
> > this is strictly a DOS-thing, or an Ada-thing, or something else.
>
> This is kind of a Unix thing. You write error and processing
> messages to stderr so they don't interfer with the data flow
> (Unix uses pipes a lot).
OK, I can't argue with that.
> I can't remember how you redirect stderr to stdout in DOS
> (but it should be in the manuals).
Hmm. I could be wrong, but I don't think there is any reasonable way to
manage stderr. Definitely no command-line directive (like piping), and
I can't find any command in the reference. Oh, well. Not a big deal.
Steve
|
|
1 Message in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
