Re: RFC 331 (v2) Consolidate the $1 and C<\1> notations
[email protected] (Dave Storrs) Tue, 3 Oct 2000 09:02:13 -0700 (PDT)
| Newsgroups | perl.perl6.language.regex |
|---|---|
| Message-ID | <Pine.BSF.4.10.10010030855240.19656-100000@megazone23.bigpanda.com> |
On Mon, 2 Oct 2000, Bart Lateur wrote: > On Mon, 2 Oct 2000 12:46:06 -0700 (PDT), Dave Storrs wrote: > > > Well, the main reason is that @/ worked best for my particular > >brain. > > But you cannot use it in an ordinary regex, can you? There's no way you > can put $/[1] between slashes in s/.../.../. BAckslashing it doesn't > work. True...which means that either perl does Deep Magic to allow it (a solution I don't like) or (the solution I DO like) the programmer uses different delimiters on pattern matchs that will contain the @/ variable...which is a good hint that something unusual is happening, which is a good thing. > >@& > >wouldn't be quite the right match...after all, $& contains the _string_ > > No, but it's closer. $& is closer in meaning to $1 than is, for example, > $/. *Much* closer. Hmmm...I see your point. I've frozen the RFC as per deadline...Nate, is it too late for me to make a minor semantic change and rename a proposed variable? Dave