From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: GNU Pascal (gpc) 2.1 released Date: Fri, 24 May 2002 21:51:10 +0100 Lines: 25 Message-ID: <3CEEA7BE.8E036E64@phekda.freeserve.co.uk> References: <3CED528D DOT 7DCF9660 AT yahoo DOT com> <3CED6BA6 DOT 48D4D0FE AT phekda DOT freeserve DOT co DOT uk> <200205241404 DOT g4OE4Qt03777 AT envy DOT delorie DOT com> <3CEE7DCE DOT BD8CACAE AT yahoo DOT com> NNTP-Posting-Host: modem-7.arkansas.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news6.svr.pol.co.uk 1022273678 4407 62.137.55.7 (24 May 2002 20:54:38 GMT) NNTP-Posting-Date: 24 May 2002 20:54:38 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. CBFalconer wrote: [snip] > Which means that "rm @foo" cannot mean to remove the file "@foo", > because if it exists it is an extended command line, and if it > doesn't it becomes an argument. So, at least for rm, that usage > makes no sense. For other programs it is another matter. [snip] FWIW this works analogously to shell wildcards do. In bash try: rm -v somefilethatdoesnotexist*.foo where nothing matches the wildcard. You should find that 'somefilethatdoesnotexist*.foo' is not expanded, because it doesn't match anything. I'm not saying this behaviour makes sense, just that the treatment of '@foo' is analogous. Regards, -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]