Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!emory!hubcap!ncrcae!opusc!yarnall
From: yarnall@opusc.csd.scarolina.edu (Ken Yarnall)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Pipes
Message-ID: <1990Nov8.040930.14630@opusc.csd.scarolina.edu>
Date: 8 Nov 90 04:09:30 GMT
References: <99.273647DB@myamiga.UUCP>
Organization: Math Department, University of South Carolina (ahem; The USC)
Lines: 27

In article <99.273647DB@myamiga.UUCP> smp@myamiga.UUCP (Steve Palm) writes:
+My suggestion is to leave the current wildcard regular expressions alone.
+They are great.  Perhaps add * for those out there who can't stomach #?.

Done in 2.0.  I think that the pttern matching syntax was augmented a bit,
actually.

+For the pipe, leave it as |.  After all, as someone pointed out, overloading
+this regular expression character works splendidly well and doesn't reserve
+yet another character.  Besides, I believe that it would be clear when you 
+wanted it to be a pipe character and when it was part of an expression.

That's the problem...it isn't always clear, unless you require whitespace
around the | when it is used as a pipe symbol.  And even then, what happens
when a filename has a space in it?  Hmmmmm, I guess you have to use quotes in
that case (something like: del "(test |test)me" to delete both `testme' and
`test me'), so that's okay.  still, it seems less confusing to use a new
symbol.

+     ///  AMIGA: | Steve Palm, Sysop of FidoNet node 1:11/16

ken
-- 
     Ken Yarnall                 ///   yarnall@usceast.cs.scarolina.EDU
      Math Department, USC   \\\///   yarnall@ucseast.UUCP
       Columbia, S.C. 29208   \\\/   (803)777-5218
    `You'd better tie me up.' -- from the movie, "Tie Me Up, Tie Me Down"