Searched refs:possessive (Results 1 – 10 of 10) sorted by path
/PHP-5.5/ext/mbstring/oniguruma/ |
H A D | HISTORY | 1562 2003/06/04: [spec] {n,m}+ should not be possessive operator. 1576 2003/05/28: [new] possessive repeat operator. (?+, *+, ++, {n,m}+)
|
H A D | regparse.c | 2284 int possessive; member 3177 tok->u.repeat.possessive = 0; in fetch_token() 3188 tok->u.repeat.possessive = 1; in fetch_token() 3192 tok->u.repeat.possessive = 0; in fetch_token() 5386 if (tok->u.repeat.possessive != 0) { in parse_exp()
|
/PHP-5.5/ext/mbstring/oniguruma/doc/ |
H A D | RE | 126 possessive (greedy and does not backtrack after repeated) 132 ({n,m}+, {n,}+, {n}+ are possessive op. in ONIG_SYNTAX_JAVA only) 389 + add possessive quantifier. ?+, *+, ++
|
/PHP-5.5/ext/pcre/pcrelib/ |
H A D | ChangeLog | 132 34. The JIT compiler should restore the control chain for empty possessive 240 12. A possessive capturing group such as (a)*+ with a minimum repeat of zero 316 34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with 383 level, when possessive repeated groups should always return to a higher 742 before the possessive +. It now does. 744 38. The use of \K (reset reported match start) within a repeated possessive 2070 5. A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive 2290 was a minimum greater than 1 for a wide character in a possessive 2856 17. Specifying a possessive quantifier with a specific limit for a Unicode 2859 are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that [all …]
|
H A D | HACKING | 253 minimizing versions. Those with "POS" in their names are possessive versions. 416 respectively (see below for possessive repetitions). All three are followed by 449 When a repeated group (capturing or non-capturing) is marked as possessive by
|
H A D | pcre_exec.c | 3329 possessive = TRUE; in match() 3344 possessive = TRUE; in match() 3352 possessive = TRUE; in match() 3360 possessive = TRUE; in match() 3730 possessive = TRUE; in match() 3738 possessive = TRUE; in match() 3746 possessive = TRUE; in match() 3754 possessive = TRUE; in match() 4096 possessive = TRUE; in match() 4103 possessive = TRUE; in match() [all …]
|
H A D | pcre_jit_compile.c | 1245 int possessive = 0; in get_framesize() local 1264 possessive = length = (common->capture_last_ptr != 0) ? 5 : 3; in get_framesize() 1416 if (SLJIT_UNLIKELY(possessive == length)) in get_framesize()
|
/PHP-5.5/ext/pcre/pcrelib/doc/ |
H A D | pcre.txt | 1494 a non-possessive quantifier. Similarly, if an atomic group is present, 4815 PCRE from making quantifiers possessive when what follows cannot match 4936 also "possessive quantifier" 6430 simpler notation, called a "possessive quantifier" can be used. This 6436 Note that a possessive quantifier can be used with an entire group, for 7861 ?+ 0 or 1, possessive 7864 *+ 0 or more, possessive 7867 ++ 1 or more, possessive 7871 {n,m}+ at least n, no more than m, possessive 7874 {n,}+ n or more, possessive [all …]
|
/PHP-5.5/ext/pcre/pcrelib/testdata/ |
H A D | testinput2 | 3968 /-- End of special auto-possessive tests --/
|
H A D | testoutput2 | 13993 /-- End of special auto-possessive tests --/
|
Completed in 99 milliseconds