Lines Matching refs:x
53 string itself. For example: /^(?:(?(1)x|)+)+$()/.
85 /(?:|a|){100}x/ are analysed.
188 pattern /(x)|((*ACCEPT))/ when matched against "abcd".
390 9. Give a compile-time error for \o{} (as Perl does) and for \x{} (which Perl
415 14. If a character class started [\Qx]... where x is any character, the class
501 the alternative cases were added to the class. For example, s and \x{17f}
592 data item and had a minimum repetition of zero (for example, [^\x{100}]* in
682 23. Perl now gives an error for missing closing braces after \x{... instead of
1075 1.4x speedup compared to the old one.
1194 26. When PCRE_UCP was not set, \w+\x{c4} was incorrectly auto-possessifying the
1195 \w+ when the character tables indicated that \x{c4} was a word character.
1236 the same checks as \x{...} characters in non-JavaScript mode. Specifically,
1294 11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
1295 "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
1297 also returns the mark "x". This bug applied to capturing parentheses,
1333 5. Supporting of \x, \U and \u in JavaScript compatibility mode based on the
1449 such as /(a)(b)x|abc/ matched against "abc", where the return code
1544 \x{...} escapes in subject strings. The has been rewritten to avoid using
2202 13. Now that we have gone to the x.xx style of version numbers, the minor
2289 8. A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
2291 repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
2554 references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
2557 5. In pcretest, an escape such as \x{de} in the data was always generating
2883 crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
2999 character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
3122 characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
3396 length. The relevant options are -x, and -i in UTF-8 mode. The result was
3403 /(?-x: )/x
3404 /(?x)(?-x: \s*#\s*)/
3405 /((?i)[\x{c0}])/8
3406 /(?i:[\x{c0}])/8
3502 For example, the pattern (?>\x{100}*)\d(?R) provoked this error
3549 escaped with \Q...\E, or parentheses in a #-comment in /x mode.
3613 processing dot, circumflex, or dollar metacharacters, or #-comments in /x
3634 to pcre_chartables.c because without it, gcc 4.x may remove the array
3750 /\500|\x{1ff}/ matches \500 or \777 because the whole thing is treated as a
4020 23. Recognize \x{...} as a code point specifier, even when not in UTF-8 mode,
4206 (a) Refactored how -x works; insert ^(...)$ instead of setting
4523 (x(y(?2))z)? provoked this bug with a subject that got as far as the
4759 whitespace in /x regexes too, which is the same as Perl. Note that the POSIX
4803 documentation calls "once-only subpatterns". A pattern such as x*+ is the same
4804 as (?>x*). In other words, if what is inside (?>...) is just a single repeated
4823 "a(?x: b c )d" did not match "XabcdY" but did match "Xa b c dY". It should have
4826 16. PCRE now gives errors for /[.x.]/ and /[=x=]/ as unsupported POSIX
4827 features, as Perl does. Previously, PCRE gave the warnings only for /[[.x.]]/
4828 and /[[=x=]]/. PCRE now also gives an error for /[:name:]/ because it supports
5131 mode, for example: \x{100}{2,3}.
5140 greater than 255. For example: [ab\x{100}-\x{400}].
5481 the letter 'x'. On long subject strings, this gives a significant speed-up.
5611 value of one (e.g. [^x]{1,6} ) was not compiled correctly. This could lead to
