Doc #62428 [Opn->Ver]: PCRE "\g" escape missing "<name>" in documentation

From: Date: Mon, 27 Apr 2015 16:08:15 +0000
Subject: Doc #62428 [Opn->Ver]: PCRE "\g" escape missing "<name>" in documentation
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-12262@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=62428&edit=1

 ID:                 62428
 Updated by:         cmb@php.net
 Reported by:        danielklein at airpost dot net
 Summary:            PCRE "\g" escape missing "<name>" in documentation
-Status:             Open
+Status:             Verified
 Type:               Documentation Problem
 Package:            PCRE related
 PHP Version:        5.4.4
 Block user comment: N
 Private report:     N

 New Comment:

Thanks, Daniel, for pointing out \g'name'. For reference: <http://3v4l.org/qsZAQ>.


Previous Comments:
------------------------------------------------------------------------
[2015-04-25 08:04:26] danielklein at airpost dot net

Thanks for the patch! I just checked \g'name' and that can be used too. I got the same
results by checking the link you provided (PHP==4.4.9 and PHP>=5.2.7).

------------------------------------------------------------------------
[2015-04-23 11:53:15] cmb@php.net

The following patch has been added/updated:

Patch Name: angle-brackets
Revision:   1429789995
URL:        https://bugs.php.net/patch-display.php?bug=62428&patch=angle-brackets&revision=1429789995

------------------------------------------------------------------------
[2015-04-23 11:52:59] cmb@php.net

Indeed, \g<name> is not documented yet. The feature is available
since 5.2.7.[1]

[1] <http://3v4l.org/tfeSh>

------------------------------------------------------------------------
[2015-04-23 03:34:47] danielklein at airpost dot net

I don't see any change. Where does it say \g<name> in the documentation?

------------------------------------------------------------------------
[2015-04-15 14:15:31] ppaisndud at gmail dot com

Documentation has been fixed, can be closed

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=62428


--
Edit this bug report at https://bugs.php.net/bug.php?id=62428&edit=1


Thread (9 messages)

« previous php.doc.bugs (#12262) next »