Searched refs:possessive (Results 1 – 16 of 16) sorted by relevance
| /external/rust/crates/grpcio-sys/grpc/third_party/re2/doc/ |
| D | syntax.txt | 44 x*+ zero or more «x», possessive NOT SUPPORTED
45 x++ one or more «x», possessive NOT SUPPORTED
46 x?+ zero or one «x», possessive NOT SUPPORTED
47 x{n,m}+ «n» or ... or «m» «x», possessive NOT SUPPORTED
48 x{n,}+ «n» or more «x», possessive NOT SUPPORTED
49 x{n}+ exactly «n» «x», possessive NOT SUPPORTED
61 (?>re) possessive match of «re» NOT SUPPORTED
62 re@> possessive match of «re» NOT SUPPORTED vim
|
| /external/pcre/dist2/ |
| D | HACKING | 495 versions. Those with "POS" in their names are possessive versions. Other kinds
668 respectively, and OP_KETRPOS for possessive repetitions (see below for more
701 When a repeated group (capturing or non-capturing) is marked as possessive by
|
| D | ChangeLog | 292 is made possessive and applied to an item in parentheses, because a
1001 encountered a character class with a possessive repeat, for example [a-f]{3}+.
1717 possessive. This is a very minor optimization.
1815 37. The JIT compiler should restore the control chain for empty possessive
2120 13. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
2328 15. A possessive capturing group such as (a)*+ with a minimum repeat of zero
|
| /external/pcre/dist2/doc/ |
| D | pcre2.txt | 5693 However, possessive quantifiers can make a difference when what follows
5700 a non-possessive quantifier. Similarly, if an atomic group is present,
6260 quantifiers possessive when what follows cannot match the repeated
6420 + 1 or more quantifier; also "possessive quantifier"
8059 pler notation, called a "possessive quantifier" can be used. This con-
8065 Note that a possessive quantifier can be used with an entire group, for
8073 meaning of a possessive quantifier and the equivalent atomic group,
8074 though there may be a performance difference; possessive quantifiers
8077 The possessive quantifier syntax is an extension to the Perl 5.8 syn-
8426 there can be no backtracking for the .*+ item because of the possessive
[all …]
|
| /external/pcre/dist2/testdata/ |
| D | testinput1 | 5900 # a possessive + to the definition of <phrase> reduced the match limit in PCRE2
5912 (?<CFWS> (?: (?&FWS)?+ (?&comment) )* (?# NOT possessive)
|
| D | testoutput1 | 9454 # a possessive + to the definition of <phrase> reduced the match limit in PCRE2
9466 (?<CFWS> (?: (?&FWS)?+ (?&comment) )* (?# NOT possessive)
|
| D | testinput2 | 3850 # End of special auto-possessive tests
|
| D | testoutput2 | 13178 # End of special auto-possessive tests
|
| /external/icu/icu4j/demos/src/com/ibm/icu/dev/demo/translit/resources/ |
| D | Transliterator_Kanji_English.txt | 3450 的>'[possessive]';
|
| /external/pcre/dist2/src/ |
| D | pcre2_jit_compile.c | 1936 int possessive = 0; in get_framesize() local
1955 possessive = length = (common->capture_last_ptr != 0) ? 5 : 3; in get_framesize()
2111 if (SLJIT_UNLIKELY(possessive == length)) in get_framesize()
|
| /external/protobuf/ |
| D | CHANGES.txt | 1924 rather than building an NFA). Worked around by making use of possessive
|
| /external/freetype/ |
| D | ChangeLog.25 | 2291 (string_re): Avoid `possessive quantifiers', which have been
|
| /external/libtextclassifier/native/annotator/pod_ner/test_data/ |
| D | vocab.txt | 22106 possessive
|
| /external/jline/src/src/test/resources/jline/example/ |
| D | english.gz | |
| /external/icu/icu4j/main/shared/data/ |
| D | Transliterator_Han_Latin_Definition.txt | 11461 的 < possessive;
43674 的 > possessive;
|
| /external/cldr/tools/java/org/unicode/cldr/util/data/transforms/ |
| D | en-IPA.txt | 4977 $x{possessive}$x → pəzɛsɪv ; # pəzɛsɑɪv pɑsɛsɑɪv
|