Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!sharkey!atanasoff!jwright
From: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Newsgroups: comp.sys.amiga
Subject: Re: AmigaDos vs Unix wildcards/pathnames
Message-ID: <876@atanasoff.cs.iastate.edu>
Date: 13 Mar 89 19:36:28 GMT
References: <11135@ut-emx.UUCP> <6235@cbmvax.UUCP>
Reply-To: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Organization: Iowa State U. Computer Science Department, Ames, IA
Lines: 33

In article <6235@cbmvax.UUCP> daveh@cbmvax.UUCP (Dave Haynie) writes:
|in article <11135@ut-emx.UUCP>, mjl@ut-emx.UUCP (Maurice LeBrun) says:
|>
|	Delete #?(.cp|.h|%) 

Is "%" a literal character in this context or is it a pattern
matching specification?  I think much, if not most, of the
perceived problems with AmigaDOS wildcards comes from the fact
that a lot of people already know Unix (or even MSDOS) wildcards,
but AmigaDOS ones don't *seem* to be well documented to for
the average user.  It's hard to use them without knowing them.

|> 1> copy (*.c|*.h) t:    (what's wrong with `cp *.c *.h t:' ??)
|
|That's a detail of the AmigaDOS copy program, not the wild card system.

Which leads to what I consider the other half of the problem.
Making use of the full wildcarding system should be trivially
simple for programmers.  If it were easy to get at, everyone
would use it.  Sounds like a great candidate for library routines
to me.

|Apollo Aegis wild cards are just plain weird, though
|on very simple level look like a UNIX/Amiga hybrid.

Confirmed member, Aegis-bashers anonymous.  :-)

|> Maurice LeBrun		      |   "So then I says to Borg, `You know,
|Dave Haynie  "The 32 Bit Guy"     Commodore-Amiga  "The Crew That Never Rests"
|   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: D-DAVE H     BIX: hazy
-- 
Jim Wright
jwright@atanasoff.cs.iastate.edu