Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-17 Thread Hugo
mike mulligan writes: :From: Hugo <[EMAIL PROTECTED]> :Sent: Tuesday, September 12, 2000 2:54 PM : :> 3. The regexp is matched left to right: first the lookbehind, then 'X', :> then '[yz]'. : :Thanks for the insight - I was stuck in my bad assumption that the optimized :behavior was the only behav

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-14 Thread Hugo
In <2914020627.B1479@yogi>, Peter Heslin writes: [...] :Bart pointed out that it would be more consistent to use the type of :syntax you have also (unconsciously?) used: : :"abcdef...xyz" =~ /(?<=x+)y/ Nothing unconscious about it: I was suggesting that the cleanest way to add VLLB would be t

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-13 Thread Robert Mathews
Hugo wrote: > The difficulty with variable-length lookbehind (let's call it > VLLB) is this: suppose that we want to match "abcdef...xyz" =~ > /(?<=x+)y/. In theory, to check the possible /x+/ matches in > the right order [0] we need to check whether there we can match > 0 characters at offset 0 (

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-13 Thread Peter Heslin
On Tue, Sep 12, 2000 at 05:16:17AM +0100, Hugo wrote: > :Simply put, I want variable-length lookbehind. > > The difficulty with variable-length lookbehind (let's call it > VLLB) is this: suppose that we want to match "abcdef...xyz" =~ > /(?<=x+)y/. In theory, to check the possible /x+/ matches in

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-13 Thread mike mulligan
From: Hugo <[EMAIL PROTECTED]> Sent: Tuesday, September 12, 2000 2:54 PM > 3. The regexp is matched left to right: first the lookbehind, then 'X', > then '[yz]'. Thanks for the insight - I was stuck in my bad assumption that the optimized behavior was the only behavior. What I am not sure of is

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-12 Thread Hugo
In <085601c01cc8$2c94f390$[EMAIL PROTECTED]>, "mike mulligan" w rites: :From: Hugo <[EMAIL PROTECTED]> :Sent: Monday, September 11, 2000 11:59 PM : : :> mike mulligan replied to Peter Heslin: :> : ... it is greedy in the sense of the forward matching "*" or "+" :constructs. :> : [snip] :> :> This

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-12 Thread mike mulligan
From: Hugo <[EMAIL PROTECTED]> Sent: Monday, September 11, 2000 11:59 PM > mike mulligan replied to Peter Heslin: > : ... it is greedy in the sense of the forward matching "*" or "+" constructs. > : [snip] > > This is nothing to do with greediness and everything to do with > left-to-rightness. T

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-11 Thread Hugo
Peter Heslin writes: :On Wed, Aug 30, 2000 at 11:54:29PM -0400, Mark-Jason Dominus wrote: :> Perhaps Hugo van der Sanden :> would be willing to discuss this with you in more detail? : :I am not acquainted with the gentleman you name. Please do solicit :the input of others you know who might be in

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-11 Thread Hugo
mike mulligan replied to Peter Heslin: :> Simply put, I want variable-length lookbehind. : :The RFC seems to say you want this so that you can optimize the operation of :the regex execution. I've been looking at the existing fixed-length :look-behind and see that it does not seem to operate the w

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-05 Thread Bart Lateur
On Sat, 2 Sep 2000 15:16:20 -0400, Peter Heslin wrote: >> This looks more natural to me: >> >> /(?`!G+A+T+)GA+C/ >Your version is closer to the way lookbehind works now, so this syntax >might be thought to be clearer; I should add to the RFC an explicit >note about this. Look at your orig

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-05 Thread mike mulligan
From: Peter Heslin <[EMAIL PROTECTED]> Sent: Thursday, August 31, 2000 10:49 PM > Simply put, I want variable-length lookbehind. The RFC seems to say you want this so that you can optimize the operation of the regex execution. I've been looking at the existing fixed-length look-behind and see t

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-02 Thread Peter Heslin
On Sat, Sep 02, 2000 at 01:52:09PM +0200, Bart Lateur wrote: > On 1 Sep 2000 20:50:20 -, Perl6 RFC Librarian wrote: > > >Imagine a very long input string containing data such as this: > > > >... GCAAGAATTGAACTGTAG ... > > > >If you want to match text that matches /GA+C/, but not when it >

Re: RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-02 Thread Bart Lateur
On 1 Sep 2000 20:50:20 -, Perl6 RFC Librarian wrote: >Imagine a very long input string containing data such as this: > >... GCAAGAATTGAACTGTAG ... > >If you want to match text that matches /GA+C/, but not when it >follows /G+A+T+/, you cannot at present do so easily. Under this >proposal

RFC 72 (v3) Variable-length lookbehind: the regexp engine should also go backward.

2000-09-01 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Variable-length lookbehind: the regexp engine should also go backward. =head1 VERSION Maintainer: Peter Heslin <[EMAIL PROTECTED]> Date: 9 Aug 2000 Last Modified: 1 Sep 2000 Mailing List: [EMAIL PR