Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!rex!wuarchive!texbell!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Regular expressions vs. file name generation  (Was: Re: Pipes)
Message-ID: <5806@sugar.hackercorp.com>
Date: 10 Jun 90 02:04:00 GMT
References: <2533@zipeecs.umich.edu> <136735@sun.Eng.Sun.COM> <12391@cbmvax.commodore.com> <36467@sequent.UUCP>
Reply-To: peter@sugar.hackercorp.com (Peter da Silva)
Organization: Sugar Land Unix - Houston
Lines: 17

In article <36467@sequent.UUCP> cseaman@sequent.UUCP (Chris "I'm Outta Here, Man!" Seaman) writes:
> Although the Bourne shell could not match the
> power of the above statement, csh and ksh can.  I would implement it
> in csh as follows:

>     ls file{[ab],c{e*,}??}.[co]

Fine. How about "All files matching a legal C format statement?"

%(|(|-)(*|#(0|1|2|3|4|5|6|7|8|9)))(|.(*|#(0|1|2|3|4|5|6|7|8|9)))(|l)(d|f|o|g|x|c)

(more or less).
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ My other car is a hot-air balloon.
      v  "Have you hugged your wolf today?" `-_-'