Lines Matching refs:what
280 int what, void *where);
284 int pcre16_config(int what, void *where);
323 16-bit library. This page describes what is different when you use the
611 int what, void *where);
615 int pcre32_config(int what, void *where);
655 describes what is different when you use the 32-bit library.
1416 single path through the tree, checking that the subject matches what is
1488 sessive quantifiers can make a difference when what follows could also
1489 match what is quantified, for example in a pattern like this:
1666 int what, void *where);
1670 int pcre_config(int what, void *where);
1866 the \n or \r escape sequences, nor does it affect what \R matches,
1900 int pcre_config(int what, void *where);
1969 The output is an integer whose value indicates what character sequences
2133 These options (which are mutually exclusive) control what the \R escape
2689 int what, void *where);
2707 PCRE_ERROR_BADOPTION the value of what was invalid
2721 PCRE_INFO_SIZE, /* what is required */
2836 ticular pattern. See the pcrejit documentation for details of what can
3258 These options (which are mutually exclusive) control what the \R escape
3512 this is called "capturing" in what follows, and the phrase "capturing
3993 behaviour may not be what you want (see the next section).
4355 that what follows cannot be part of the repeat. For example, a+[bc] is
4470 what it was outside the recursion, as do the values of all captured
4549 1. PCRE has only a subset of Perl's Unicode support. Details of what it
4553 they do not mean what you might think. For example, (?!a){3} does not
4815 PCRE from making quantifiers possessive when what follows cannot match
4857 does not affect what the \R escape sequence matches. By default, this
6030 (*CRLF) to override what the application has set or what has been
6386 repetition, failure of what follows normally causes the repeated item
6729 and then see if what follows matches the rest of the pattern. If the
7091 Back at the top level, the next character ("c") is compared with what
7280 The new verbs make use of what was previously invalid syntax: an open-
7410 tinues with what follows, but if there is no subsequent match, causing
7420 These verbs differ in exactly what kind of failure occurs when back-
7421 tracking reaches them. The behaviour described below is what happens
8045 what happens afterwards. Those that advance the start-of-match point do
8330 is described in what follows. If you are using the 16-bit library, sub-
8473 what is counted are not the same. The PCRE_ERROR_RECURSIONLIMIT error
8627 (6) OK, the stack is for long term memory allocation. But what happens
8737 that what has been typed so far is potentially valid, it is able to
9008 this may or may not be what you want. The only way to allow for start-
9044 characters that precede the start of what would be returned for a com-
9094 what might be considered a partial match of an empty string actually
9277 study data, and this is what you must save (not the pcre[16|32]_extra
10141 bility of matching an empty string. Comments in the code explain what
10393 of 500 bytes mentioned above may be larger or smaller than what is
