Re: Questions concerning /o regex modifier

Well... there is that rare and special occasion when the variable changes and you don't want the regex to change...

Remember we are talking about backwards compatibility and not good coding practices when I say this :)

- Ant
- Some of my best work - (1 2 3)

Comment on Re: Questions concerning /o regex modifier

Replies are listed 'Best First'.
Re^2: Questions concerning /o regex modifier by Limbic~Region (Chancellor) on Nov 29, 2006 at 15:55 UTC
suaveant, Yes for extremely old versions that did not support qr// it was useful. My question regarding deprecation stands. In very old versions the deprecated warning won't appear but in newer versions where it is not necessary it will. Makes good sense to me. Cheers - L~R	[reply]
Re^3: Questions concerning /o regex modifier by suaveant (Parson) on Nov 29, 2006 at 16:11 UTC
I could see deprecating it... especially since very little that gets deprecated ever actually goes away anyway. No old code would actually break but they would get warnings. I wonder how it is being handled in Perl6... maybe you just have to wait a bit. - Ant - Some of my best work - (1 2 3)	[reply]
Re^4: Questions concerning /o regex modifier by idsfa (Vicar) on Nov 29, 2006 at 17:09 UTC
The jury is still out on the `/o` modifier in perl 6, but it's not looking like it will be needed: Several modifiers, /x, /s, and /m, are no longer needed and have been retired. It's unclear whether /o is necessary any more. We will assume it's gone unless it's shown that caching can't handle the problem. Note that the regex now has more control over when to cache subrules because it is no longer subject to the vagaries of standard interpolation. The intelligent reader will judge for himself. Without examining the facts fully and fairly, there is no way of knowing whether vox populi is really vox dei, or merely vox asinorum. — Cyrus H. Gordon	[reply] [d/l]