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.
>@&
>wouldn't be quite the right match...after all, $& contains the _string_
>that was last matched, while @/ contains the pattern and all the
>subelements that matched, but does not actually contain the entire matched
>string (unless you explicitly capture it, of course).
No, but it's closer. $& is closer in meaning to $1 than is, for example,
$/. *Much* closer.
--
Bart.
