Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!ogicse!intelhf!agora!billsey
From: billsey@agora.uucp (Bill Seymour)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Pipes
Message-ID: <1990Nov8.173836.19620@agora.uucp>
Date: 8 Nov 90 17:38:36 GMT
References: <99.273647DB@myamiga.UUCP>
Organization: Open Communications Forum
Lines: 30

In article <99.273647DB@myamiga.UUCP> smp@myamiga.UUCP (Steve Palm) writes:
:I would never have guessed that such a great amount of bandwith could be taken 
:up with such a simple topic as pipes and wildcards...  Live and learn...
: 
:My suggestion is to leave the current wildcard regular expressions alone.
:They are great.  Perhaps add * for those out there who can't stomach #?.
: 
: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.

	But if we now reserve | for a pipe, what will I use for an 'OR'? That's
what | is used for now in the AmigaDOS pattern matching... I would be all for
using it in piping, if it hadn't been used before.
	BTW, now that we have a 'NOT' (~) in the pattern matching algorythm,
any chance for [a-m,o-z] type patterns?

:--  
:     ///  AMIGA: | Steve Palm, Sysop of FidoNet node 1:11/16
:    ///  FOR THE | UUCP: {gatech,ames,rutgers}!ncar!asuvax!stjhmc!myamiga!smp
:\\\///  CREATIVE | INTERNET: [not yet available]
: \XX/     MIND   |_________________________________________________________ 


-- 
     -Bill Seymour                                            billsey@agora
***** American People/Link Amiga Zone Hardware Specialist  NES*BILL *****
Bejed, Inc.       NES, Inc.        Northwest Amiga Group    At Home Sometimes
(503) 281-8153    (503) 246-9311   (503) 656-7393 BBS       (503) 640-0842