Lines Matching refs:mode
102 pattern that begins with "(*UTF8)" or "(*UTF)" turns on UTF-8 mode,
429 In 16-bit mode, when PCRE_UTF16 is not set, character values are
430 treated in the same way as in 8-bit, non UTF-8 mode, except, of course,
436 In UTF-16 mode, the character code is Unicode, in the range 0 to
453 patterns in the other mode, for example, if a pattern compiled with
760 In 32-bit mode, when PCRE_UTF32 is not set, character values are
761 treated in the same way as in 8-bit, non UTF-8 mode, except, of course,
767 In UTF-32 mode, the character code is Unicode, in the range 0 to
782 to a function that processes patterns in the other mode, for example,
1849 dollar metacharacters, the handling of #-comments in /x mode, and, when
2073 mode. It may sometimes point into the middle of a UTF-8 or UTF-16 char-
2132 changed within a pattern by a (?i) option setting. In UTF-8 mode, PCRE
2300 library, the last two are recognized only in UTF-8 mode.
2319 characters, and so are ignored in this mode. Also, an unescaped # out-
2401 ASCII strings, even in 16-bit or 32-bit mode. As PCRE has developed,
2456 51 octal value is greater than \377 in 8-bit non-UTF-8 mode
2471 64 ] is an invalid data character in JavaScript compatibility mode
2590 which to start matching. (In 16-bit mode, the bitmap is used for 16-bit
2591 values less than 256. In 32-bit mode, the bitmap is used for 32-bit
2614 by character code point. When running in UTF-8 mode, or in the 16- or
2741 ever, this means that when the 32-bit library is in non-UTF-32 mode,
2773 mode the value can be up to 0x10ffff, and up to 0xffffffff when not
2774 using UTF-32 mode.
2844 Since for the 32-bit library using the non-UTF-32 mode, this function
2878 value is -1. The value is a number of characters, which in UTF mode may
3301 in multiline mode) a newline immediately before it. Setting this with-
3455 and this is by far the most common case. In UTF-8 or UTF-16 mode, the
3457 ject (in UTF-32 mode, one data unit equals one character, so all off-
3524 sets, even in UTF mode. They are byte offsets in the 8-bit library,
3753 using a JIT compile option is being matched, but the matching mode
3755 mode. When the JIT fast path function is used, this error may be also
4646 16. Perl, when in warning mode, gives warnings for character classes
4783 setting the relevant option. How setting a UTF mode affects pattern
4894 matched independently of case. In a UTF mode, PCRE always understands
4913 ^ assert start of string (or line, in multiline mode)
4914 $ assert end of string (or line, in multiline mode)
4955 In a UTF mode, only ASCII numbers and letters have any special meaning
5005 \x{hhh..} character with hex code hhh.. (non-JavaScript mode)
5006 \uhhhh character with hex code hhhh (JavaScript mode only)
5018 is, however, recognized when PCRE is compiled in EBCDIC mode, where
5019 data items are always bytes. In this mode, all values are valid after
5087 mode, support for code points greater than 256 is provided by \u, which
5092 two syntaxes for \x (or by \u in JavaScript mode). There is no differ-
5094 as \x{dc} (or \u00dc in JavaScript mode).
5101 8-bit non-UTF mode less than 0x100
5102 8-bit UTF-8 mode less than 0x10ffff and a valid codepoint
5103 16-bit non-UTF mode less than 0x10000
5104 16-bit UTF-16 mode less than 0x10ffff and a valid codepoint
5105 32-bit non-UTF mode less than 0x100000000
5106 32-bit UTF-32 mode less than 0x10ffff and a valid codepoint
5250 In 8-bit, non-UTF-8 mode, only the characters with codepoints less than
5256 any Unicode newline sequence. In 8-bit non-UTF-8 mode \R is equivalent
5304 are available. When in 8-bit non-UTF-8 mode, these sequences are of
5306 256, but they do work in this mode. The extra escape sequences are:
5565 UTF mode, the meanings of \w and \W can be changed by setting the
5574 set. Thus, they are independent of multiline mode. These three asser-
5607 Outside a character class, in the default matching mode, the circumflex
5644 (where \n represents a newline) in multiline mode, but not otherwise.
5645 Consequently, patterns that are anchored in single line mode because
5646 all branches start with ^ are not anchored in multiline mode, and a
5688 unit, whether or not a UTF mode is set. In the 8-bit library, one data
5692 match individual bytes in UTF-8 mode, but it is unclear how it can use-
5694 units, matching one unit with \C in a UTF mode means that the rest of
5702 below) in a UTF mode, because this would make it impossible to calcu-
5735 mode, the character may be more than one data unit long. A matched
5750 In UTF-8 (UTF-16, UTF-32) mode, characters with values greater than 255
5757 match "A", whereas a caseful version would. In a UTF mode, PCRE always
5762 caseless matching in a UTF mode for characters 128 and above, you must
5798 current mode.
5802 to [][\\^_`wxyzabc], matched caselessly, and in a non-UTF mode, if
5897 POSIX classes are handled specially in UCP mode:
6687 In a UTF mode, PCRE does not allow the \C escape (which matches a sin-
6688 gle data unit even in a UTF mode) to appear in lookbehind assertions,
7695 in dotall mode, any character whatsoever
7696 \C one data unit, even in UTF mode (best avoided)
7714 mode or in the 16- bit and 32-bit libraries. However, if locale-spe-
7859 also after internal newline in multiline mode
7863 also before internal newline in multiline mode
7921 (*UTF8) set UTF-8 mode: 8-bit library (PCRE_UTF8)
7922 (*UTF16) set UTF-16 mode: 16-bit library (PCRE_UTF16)
7923 (*UTF32) set UTF-32 mode: 32-bit library (PCRE_UTF32)
7924 (*UTF) set appropriate UTF mode for the library in use
8090 be used with either library. When UTF mode is set, both the pattern and
8214 2. Octal numbers up to \777 are recognized, and in UTF-8 mode they
8224 mode, or a single 16-bit data unit in UTF-16 mode, or a single 32-bit
8225 data unit in UTF-32 mode, but its use can lead to some strange effects
8229 supported in UTF mode by the JIT optimization of pcre[16|32]_exec(). If
8237 set as in non-UTF mode, all with values less than 256. This remains
8396 appropriate mode (normal or hard/soft partial), it obeys that code
8431 when running in a UTF mode, and a callout immediately before an asser-
8738 partial matches on the same pattern. If the appropriate JIT study mode
9791 RE object. The examples below use one mode or the other arbitrarily.
