Date:	Wed, 31 Jan 2001 10:10:17 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Rudolf Polzer <rpolzer AT web DOT de>
cc:	djgpp AT delorie DOT com
Subject:	Re: newbie
In-Reply-To:	<slrn97bapv.4d2.rpolzer@rebounce.rpolzer-lx>
Message-ID:	<Pine.SUN.3.91.1010131100936.29266J-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 29 Jan 2001, Rudolf Polzer wrote:

> > This will not work with programs which print error messages to stderr 
> > instead of stdout.  COMMAND.COM doesn't know how to redirect stderr.
> 
> Why is 2>&1 not implemented in command.com?

This questions should go to Microsoft.

> cmd.exe of WinNT can do it.

cmd.exe is a different program, it has many more features (many of
them unknown to most users) that command.com doesn't have.

> Or why doesnt gcc print error messages to STDOUT on WinDOZe when a
> switch like -stdout is passed?

I don't think GCC supports a -stdout switch.  Are you suggesting a new
feature?

> Since gcc does not stop at the first error
> message, you cannot find the error without the pause key or an IDE!

Then use an IDE.

- Raw text -