Lines Matching refs:P
68 16. When PCRE was compiled without UCP support, the use of \p and \P gave an
193 3. If a pattern in pcretest input had the P (POSIX) modifier followed by an
402 /(?P<Name>a)?(?P<Name2>b)?(?(<Name>)c|d)*l/
2107 13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
3065 12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
3095 20. Debugging a pattern containing \p or \P could cause a crash. For example,
3096 [\P{Any}] did so. (Error in the code for printing property names.)
3105 behind). There were bugs in these functions when a repeated \p or \P was
3116 (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
3119 (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
3126 26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
3129 27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
3130 \p or \P) caused a compile-time loop.
3215 12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
3561 as (?P<name>...). The new forms, as well as being in Perl 5.10, are
3565 (?&name) as well as (?P>name).
3568 \k'name' as well as (?P=name). The new forms, as well as being in Perl
3791 as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of
4013 21. Refactored the implementation of \p and \P so as to be more general, to
4016 \p or \P will have to recompile them.
4295 both the P and the s flags.
4386 via the \p, \P, and \X escapes. Unicode property support implies UTF-8
4403 pcre_exec() and the \P data escape in pcretest.
4840 \L, \l, \N, \P, \p, \U, \u, and \X.
4940 36. Added support for named subpatterns. The Python syntax (?P<name>...) is
4942 be unique. Back references use the syntax (?P=name) and recursive calls use
4943 (?P>name) which is a PCRE extension to the Python extension. Groups still have
