Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com
From: Darco <rquat@datasys.net>
Newsgroups: scea.yaroze.beginners
Subject: Re: How can I output gcc error list to a file?
Date: Thu, 21 Jan 1999 15:43:58 -0500
Organization: SCEA News Server
Lines: 33
Message-ID: <36A7918E.3FCBC4A4@datasys.net>
References: <70mndd$7i7@chuka.playstation.co.uk> <70osit$cv311@scea> <70rdag$dnq8@scea> <70rri8$dnq12@scea>
Reply-To: darco@bigfoot.com
NNTP-Posting-Host: 449.dialup.datasys.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.05 [en] (Win95; U)

Steve Tolin wrote:
> 
> There was a simple parameter that could be used under 95/98..   I was using
> when I first got my Yaroze because I seen it in one of the earlier posts..
> But that was about a year ago..
> 
> It might have been something like this instead  make >> errors.txt
> 
> Does this jog anyones memory???
> 

No... Sorry. ;)

But > and >> aren't exactly command line arguments... They just redirect
output to a file or a device. > overwrites, and >> ammends. The work
with (nearly) all programs and commands.

echo hello > hello.txt
echo hello > hello.txt

That would make a text file with hello in it. But this:

echo hello > hello.txt
echo hello >> hello.txt

This will make a text file with 2 hellos in it. >> is useful when you
are dealing with log files...

DJGPP-compiled DOS programs never seemed to work with this though. I
always assumed it to be because it accessed the hardware at some lower
level, being a 32 bit program rather than 16 bit.

'Darco