Uri Guttman wrote: > but we need a better syntax for s/// that doesn't modify its string but > returns a copy which has had the substitution applied to it. possibly a > s/// modifier? > > $new = $old =~ s/foo/bar/n ; > > n for new? if our internal string representation could grow from the middle instead of being a single malloc, there wouldn't be the performance hit you get from ($new = $old) =~ s/foo/bar/ or maybe it is that you just abhor parentheses? -- David Nicol 816.235.1187 [EMAIL PROTECTED] Subroutine one-arg, him called no-arg, get $_-arg. Ug.
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- copying and s/// (was Re: Overlapping RFCs 1... Uri Guttman
- Re: copying and s/// (was Re: Overlappin... Nathan Wiger
- Re: copying and s/// (was Re: Overlappin... Brad Hughes
- Re: copying and s/// (was Re: Overlappin... Mike Lambert
- Re: copying and s/// (was Re: Overlappin... Nathan Wiger
- Re: copying and s/// (was Re: Overlappin... Tom Christiansen
- Re: copying and s/// (was Re: Overlappin... Tom Christiansen
- Re: copying and s/// (was Re: Overlappin... Tom Christiansen
- Re: copying and s/// (was Re: Overlappin... Tom Christiansen
- Re: Overlapping RFCs 135 138 164 David L. Nicol
- Re: Overlapping RFCs 135 138 164 Steve Fink
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- Re: Overlapping RFCs 135 138 164 Tom Christiansen
- Re: Overlapping RFCs 135 138 164 Nathan Wiger