From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21411 invoked from network); 14 Apr 2000 11:42:19 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Apr 2000 11:42:19 -0000 Received: (qmail 901 invoked by alias); 14 Apr 2000 11:42:09 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10757 Received: (qmail 885 invoked from network); 14 Apr 2000 11:42:08 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) From: "Andrej Borsenkow" To: "Peter Stephenson" , "Zsh hackers list" Subject: RE: PATCH: fix for (#s) and (#e) in param substs Date: Fri, 14 Apr 2000 15:42:05 +0400 Message-ID: <000601bfa606$750527f0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <0FT000MKM7T8D3@la-la.cambridgesiliconradio.com> > This wasn't as bad as it could have been. Things like > > ${foo//(#s)d*time(#e)/d fight/} > > are all now supposed to work. One thing I like about this is > it allows you > to forget about not only anchor characters in / and //, but > even ## and %%, > and with the (S) parameter flag # and % too --- the /-forms > together with > the start and end assertions present a single consistent interface for > pattern substitutions. > Just a question - is there any speed penalty in using / instead of # or %? -andrej