On Thu, Mar 6, 2008 at 3:40 PM, John Cowan <[EMAIL PROTECTED]> wrote:
> Alex Shinn scripsit:
>
>
> > Chicken regexp's historically weren't tied to PCRE, and
> > provided a fairly minimal feature set to accomodate all the
> > backends equally. It now always uses PCRE, and you could
> > get at t
Alex Shinn scripsit:
> Chicken regexp's historically weren't tied to PCRE, and
> provided a fairly minimal feature set to accomodate all the
> backends equally. It now always uses PCRE, and you could
> get at the named subpatterns with pcre_get_named_substring()
> if you returned the match object
> "Hans" == Hans Nowak <[EMAIL PROTECTED]> writes:
Hans> In PCRE, a subpattern can be named in one
Hans> of three ways: (?...) or (?'name'...) as
Hans> in Perl, or (?P...) as in Python.
Yep, PCRE is "Perl Compatible" - it's an entirely separate
code-base from the Perl regexp eng
On Wed, Mar 05, 2008 at 09:55:21PM -0500, Hans Nowak wrote:
> The way I understand it, Chicken's regex module is based on PCRE,
> and the PCRE manual mentions the (?P...) syntax:
>
>In PCRE, a subpattern can be named in one of three ways: (?...)
>or (?'name'...) as in Perl, or (
Robin Lee Powell wrote:
I've just looked through "man perlre" fairly carefully and found
nothing like this at all. So I asked the Python regex
documentation:
Python adds an extension syntax to Perl's extension syntax. If
the first character after the question mark is a "P", you know
