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
On Sat, 30 Sep 2000, Bart Lateur wrote:
I wrote this before, but apparently you didn't hear it. Let me repeat:
You're right, I missed your email when I was incorporating things
into the new version. Apologies.
$foo on the LHS allows metacharacter matching, for example "a.*b" can
On Thu, 28 Sep 2000, Hugo wrote:
:=item *
:/(foo)_C\1_bar/
Please don't do this: write C/(foo)_\1_bar/ or /(foo)_\1_bar/, but
don't insert C in the middle: that makes it much more difficult to
read.
Sorry; that was a global-replace error that I missed on
proofreading.
:mean
On Fri, 29 Sep 2000, Hildo Biersma wrote:
Currently, C\1 and $1 have only slightly different meanings within a
regex. Let's consolidate them together, eliminate the differences, and
settle on $1 as the standard.
Sigh. That would remove functionality from the language.
The reason
Both \1 and $1 refer to what is matched by the first set of parens in a
regex. AFAIK, the only difference between these two notation is that \1
is used within the regex itself and $1 is used outside of the regex. Is
there any reason not to standardize these down to one notation (i.e.,
eliminate
On Wed, 27 Sep 2000, Jonathan Scott Duff wrote:
If $1 could be made to work properly on the LHS of s///, I'd vote for
that being The Way.
That was pretty much my thought?
On 27 Sep 2000, Piers Cawley wrote:
Do we *want* to maintain \1? Why have two notations to do the
I'm kind of curious about what happens when you want to do, say:
if (m/(\S+)/) {
$reg = qr{(em|i|b)($1)/\1};
}
where the $1 in the regex quote is refering to $1 from the
