One thing I'd like to see is being able to specify qr//d regexes or list
(refs) within this, to be able to give multiple equivlent objects. For
example, the list
("<<" => ">>", "\N{left gimmulet}" => "\N{right gimmulet}") would allow <<
to match >> and « to match ». However, (["<<", "\N{left gim
- Original Message -
From: "Eric Roode" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 24, 2000 1:56 PM
Subject: Re: RFC 145 (v1) Brace-matching for Perl Regular Expressions
> Well, if we stick to the model of a lowercase/uppercase pair
&g
>
>> How about \p and \P ("P" for "pairwise groupings" or just "pairs")?
>
>\p and \P already have meanings in Perl 5 also. \p{property} matches
>any single character with the specified Unicode property, and
>\P{property} is the inverse.
Crap. Okay, that's it. Perl is just gonna have to
>How about \p and \P ("P" for "pairwise groupings" or just "pairs")?
I'm afraid those are taken, too.
Symbol Atomic Meaning
-- -- ---
C<\0> yes Match the null character (ASCII NUL).
C<\I> yes Match the character given in octal, up to C<
>=head1 ABSTRACT
>It is quite difficult to match paired characters in Perl 5 regular
>expressions. A solution is proposed, using new \g (match opening grouping
>character) and \G (match closing grouping character) metacharacters.
>Two new special variables, @^g and @^G control which strings are
At 12:13 PM -0400 on 8/24/00, Mark-Jason Dominus wrote:
>The big problem I see that you didn't address is that you didn't say
>what would happen when the target string contains mismatched
>parentheses.
>
>Your example was:
>
>$string = "([b - (a + 1)] * 7)";
>$string =~ /\g.*?\G/;
>
>Now
>
>> What exactly is matched by \g and \G is controlled by two new special
>> variables, @^g and @^G, which are arrays of strings.
>
>These sorts of global variables have been a problem in the past.
>Since they change the meaning of the \g and \G escapes, I think they
>should be pragmas or some o
> What exactly is matched by \g and \G is controlled by two new special
> variables, @^g and @^G, which are arrays of strings.
These sorts of global variables have been a problem in the past.
Since they change the meaning of the \g and \G escapes, I think they
should be pragmas or some other de
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Brace-matching for Perl Regular Expressions
=head1 VERSION
Maintainer: Eric J. Roode <[EMAIL PROTECTED]>
Date: 24 Aug 2000
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: 145
=head1 ABSTRACT
