Lines Matching refs:where
280 int what, void *where);
284 int pcre16_config(int what, void *where);
611 int what, void *where);
615 int pcre32_config(int what, void *where);
884 configure script, where the optional features are selected or dese-
1110 In environments where the size of the stack is limited, this can se-
1185 PCRE assumes by default that it will run in an environment where the
1666 int what, void *where);
1670 int pcre_config(int what, void *where);
1900 int pcre_config(int what, void *where);
2570 work in cases where JIT optimization is not used, but it is advisable
2609 and you want to make use of these facilities in cases where matching
2653 and use tables that are appropriate for the French locale (where
2689 int what, void *where);
2703 the argument where was NULL
2722 &length); /* where to put the data */
2750 library, where data units are bytes. The fourth argument should point
2778 matched string in the situation where PCRE_INFO_FIRSTCHARACTERFLAGS
2915 the 8-bit library, where the first two bytes of each entry are the num-
3046 where different parts of the application may be using the same compiled
3171 where d is a decimal number. However, such a setting is ignored unless
3199 where d is a decimal number. However, such a setting is ignored unless
3366 where the result is "no match", the callouts do occur, and that items
3561 There are some cases where zero is returned (indicating vector over-
3572 slots (namely 2) have been filled. In similar cases where there is tem-
3942 However, PCRE is used in some situations where it is linked via a spe-
4108 workspace will be needed for patterns and subjects where there are a
4624 the point where they are tested.
4630 it is the same as PCRE, but there are examples where it differs.
4644 such as (?|(?<a>A)|(?<b)B), where the two capturing parentheses have
4845 tion. For example, on a Unix system where LF is the default newline
4854 The newline convention affects where the circumflex and dollar asser-
4877 where d is any number of decimal digits. However, the value of the set-
5007 \cx "control-x", where x is any ASCII character
5534 are of the form \uHHHH or \UHHHHHHHH where H is a hexadecimal digit.
5585 A word boundary is a position in the subject string where the current
5612 mentation where \G can be useful.
5668 (where \n represents a newline) in multiline mode, but not otherwise.
5800 where it cannot be interpreted as indicating a range, typically as the
5816 at a point where a range ending character is expected. For example,
5853 backslash, hyphen (only where it can be interpreted as specifying a
5902 POSIX syntax [.ch.] and [=ch=] where "ch" is a "collating element", but
6169 cate names can be useful for patterns where only one instance of the
6256 position where a quantifier is not allowed, or one that does not match
6288 for such patterns. However, because there are cases where this can be
6295 causing the rest of the pattern to fail. The classic example of where
6345 In cases where it is known that the subject string contains no new-
6349 However, there are some cases where the optimization cannot be used.
6351 reference elsewhere in the pattern, a match at the start may fail where
6359 Another case where implicit anchoring is not applied is when the lead-
6361 fail where a later one succeeds. Consider this pattern:
6634 (2) If quantifier is {0,n} where n is greater than zero, it is treated
6799 example where the alternatives are complex:
6917 strings in one of the two forms dd-aaa-dd or dd-dd-dd, where aaa are
7370 pcretest output, where the /K modifier requests the retrieval and out-
7490 character, but to the position in the subject where (*SKIP) was encoun-
7510 (*MARK) instead of to where (*SKIP) was encountered. If no (*MARK) with
7541 the enclosing alternative. Consider this pattern, where A, B, etc. are
7587 tern, where A, B, etc. are complex pattern fragments:
7693 \x where x is non-alphanumeric is a literal x
7700 \cx "control-x", where x is any ASCII character
8157 UTF-16, where they are used in pairs to encode codepoints with values
8581 where the local data of the current node is pushed before checking its
8674 for use where JIT is known to be available, and which need the best
8727 where it might be helpful to distinguish this case from other cases in
8730 Consider, for example, an application where a human is required to type
8794 is set to the offset of the character where matching started.
8798 tions, or begin with \b or \B, characters before the one where matching
8808 offset where matching began.
8984 same working space as before, because this is where details of the pre-
9024 re-run, starting from the point where the partial match occurred. Ear-
9168 where no string can be a partial match for both alternatives. This is
9357 there is one case where the memory usage of a compiled pattern can be
9450 matches the subject "first\nand second" (where \n stands for a newline
9479 where a literal character follows. Before embarking on the standard
9846 T (where "bool T::ParseFrom(const char*, int)" exists)
10290 different numbers of a's. Furthermore, in a number of cases where the
10352 In environments where stack memory is constrained, you might want to
