Date: Fri, 24 May 2002 10:04:26 -0400
Message-Id: <200205241404.g4OE4Qt03777@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <ackpus$4e5$1@antares.lu.erisoft.se> (eplmst@lu.erisoft.se)
Subject: Re: GNU Pascal (gpc) 2.1 released
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1020523191611 DOT 3394B-100000 AT is> <3CED528D DOT 7DCF9660 AT yahoo DOT com> <3CED6BA6 DOT 48D4D0FE AT phekda DOT freeserve DOT co DOT uk> <ackpus$4e5$1 AT antares DOT lu DOT erisoft DOT se>
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
Precedence: bulk


> :     bash-2.04$ rm -fv @foo
> 
> I have myself been bitten by this.
> 
> Is there any good reason why a non-existent file shouldn't produce a
> warning?

If you use the "-f" option of rm, it silences warnings.

What djgpp does is look to see if @foo means a file foo.  If the file
foo doesn't exist, the whole @foo is passed to the program as-is (that
allows you do to do things like "grep @PATH@ Makefile.in").  If the
program doesn't warn about invalid parameters, it will go unnoticed.