From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jeremy Drake <pgsql(at)jdrake(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com> |
Subject: | Re: patch adding new regexp functions |
Date: | 2007-02-16 17:49:36 |
Message-ID: | 20070216174936.GE21379@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, Feb 16, 2007 at 05:54:47PM +0100, Peter Eisentraut wrote:
> Am Freitag, 16. Februar 2007 17:11 schrieb David Fetter:
> > > As for the regexp_matches() function, it seems to me that it
> > > returns too much information at once. What is the use case for
> > > getting all of prematch, fullmatch, matches, and postmatch in
> > > one call?
> >
> > If not in one call, how would you get it? Perl, for example,
> > makes these available to any regex match in the form of variables
> > it sets.
>
> The question is, what is the use case? If there is one in Perl, can
> this proposed function API support it?
Perl makes the following variables available in any regex match,
although it optimizes some cases for when they're not there:
$1, ... $n (captured matches in parentheses)
$` (pre-match)
$' (post-match)
$& (whole match)
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2007-02-16 17:49:54 | Re: HOT for PostgreSQL 8.3 |
Previous Message | Gregory Stark | 2007-02-16 17:42:25 | Re: Mail getting through? Short varlena headers |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-02-16 18:03:32 | Re: patch adding new regexp functions |
Previous Message | Tom Lane | 2007-02-16 17:17:25 | Re: [GENERAL] ISO week dates |