Lines Matching refs:even
998 to the configure command. This implies UTF support, even if you have
1476 is no point even considering the possibility of backtracking into the
1521 matches a single data unit, even in UTF-8, UTF-16 or UTF-32 modes, is
1889 later time, possibly by a different program, and even on a host other
2082 Note that the offset is in data units, not characters, even in a UTF
2164 only ever matches one character, even if newlines are coded as CRLF.
2266 characters, even if it actually contains newlines. The "start of line"
2411 ASCII strings, even in 16-bit or 32-bit mode. As PCRE has developed,
2533 returns a pcre_extra block even if studying did not find any additional
2559 If studying succeeds (even if no data is returned), the variable it
3081 later in different processes, possibly even on different hosts. For a
3534 sets, even in UTF mode. They are byte offsets in the 8-bit library,
4145 that requires additional characters. This happens even if some complete
4198 compatibility with the way pcre_exec() returns data, even though the
4210 there is no point even considering the possibility of backtracking into
4621 action is limited to that group, even if the group does not contain any
4653 rent Perls warn that this is deprecated) but PCRE never does, even if
4704 even on different hosts that have the other endianness. However, this
6018 matches "ab", "aB", "c", and "C", even though when matching "C" the
6212 can always give the same name to subpatterns with the same number, even
6544 matches "rah rah" and "RAH RAH", but not "RAH rah", even though the
6716 gle data unit even in a UTF mode) to appear in lookbehind assertions,
7051 unset, even if it was (temporarily) set at a deeper level during the
7076 the subject string, it is never re-entered, even if it contains untried
7121 separate the two cases, and write out the odd and even cases as alter-
7190 ject string, it is never re-entered, even if it contains untried alter-
7724 \C one data unit, even in UTF mode (best avoided)
7741 By default, \d, \s, and \w match only ASCII characters, even in UTF-8
8266 true even when PCRE is built to include Unicode property support,
8321 positions in the subject, even for a single call. Therefore, if the
8450 "Controlling the JIT stack" below, even if you do not need to supply a
8571 Strictly speaking, even more is allowed. You can assign the same non-
8636 pattern at any time. You can even free the previous stack before
8721 Due to an unfortunate implementation oversight, even in versions 8.32
9053 the result is no match, even though there would be a match for "aug23"
9109 hind assertion later in the pattern could require even earlier charac-
9439 even with the outer repetition increased to 100. However, this pattern
9520 extremely long time, even for relatively short strings.
9598 are not even defined.
9610 even less compatible.
9936 Note that it's legal to escape a character even if it has no special
