Lines Matching refs:b
2349 optimization that, for example, turns a+b into a++b in order to avoid
2367 This option changes the way PCRE processes \B, \b, \D, \d, \S, \s, \W,
2768 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not
2801 (b) every branch of the pattern starts with ".*" and PCRE_DOTALL is not
2878 Note that the simple assertions \b and \B require a one-character look-
3324 a?b?
3326 is applied to a string not beginning with "a" or "b", it matches an
3329 rences of "a" or "b".
3565 (a)(?:(b)c|bd)
3966 (a+)b(?<xxx>\d+)...
4557 other assertions such as \b, but these do not seem to have any use.
4637 matching "aba" against the pattern /^(a(b)?)+$/ in Perl leaves $2
4638 unset, but in PCRE it is set to "b".
4644 such as (?|(?<a>A)|(?<b)B), where the two capturing parentheses have
4679 (b) If PCRE_DOLLAR_ENDONLY is set and PCRE_MULTILINE is not set, the $
4816 the repeated item. For example, by default a+b is treated as a++b. For
4848 (*CR)a.b
5139 class, \b is interpreted as the backspace character (hex 08).
5235 affects \b, and \B because they are defined in terms of \w and \W.
5570 \b matches at a word boundary
5578 Inside a character class, \b has a different meaning; it matches the
5590 PCRE_UCP option. When this is done, it also affects \b and \B. Neither
5592 quence. However, whatever follows \b normally determines which it is.
5802 example, [b-d-z] matches letters in the range b to d, a hyphen charac-
5838 "Generic character types" above. The escape sequence \b has a different
5950 [[:<:]] is converted to \b(?=\w)
5951 [[:>:]] is converted to \b(?<=\w)
5954 [a[:<:]b] provokes error for an unrecognized POSIX class name. This
5957 that \b matches at the start and the end of a word (see "Simple asser-
6012 (a(?i)b)c
6020 (a(?i)b|c)
6363 (?>.*?a)b
6378 /(a|(b))+/
6380 matches "aba" the value of the second captured substring is "b".
6590 (a|b\1)+
6609 The simple assertions coded as \b, \B, \A, \G, \Z, \z, ^ and $ are
6892 \b (?&byte) (\.(?&byte)){3} \b
7088 tern 1 successfully matches the next character ("b"). (Note that the
7152 match "b", then in the second group, when the back reference \1 fails
7153 to match "b", the second alternative matches "a" and then recurses. In
7154 the recursion, \1 does now match "b" and so the whole match succeeds.
7435 a+(*COMMIT)b
7494 a+(*SKIP)b
7564 ^.*? (?(?=a) a | b(*THEN)c )
7568 then fails, the character "b" is matched, but "c" is not. At this
7573 match "b", the match would succeed.)
7609 /(a(*COMMIT)b)+ac/
7880 \b word boundary
8258 6. The character escapes \b, \B, \d, \D, \s, \S, \w, and \W correctly
8264 in particular that this applies to \b and \B, because they are defined
8798 tions, or begin with \b or \B, characters before the one where matching
8824 match at the end of the subject, as normal, and for \b and \B the end
8847 data, and so, if \z, \Z, \b, \B, or $ are encountered at the end of the
8917 If a pattern ends with one of sequences \b or \B, which test for word
8921 /\bcat\b/
8926 However, normal matching carries on, and \b matches at the end of the
9029 \z, \Z, \b, \B, and $. Consider an unanchored pattern that matches
9043 with \b or \B, the string that is returned for a partial match includes
9110 arises if the pattern ends with \b or \B. Another kind of difference
9430 By default, the escape sequences \b, \d, \s, and \w, and the POSIX
9437 much difference for \b.
9477 (a+)*b
9480 matching procedure, PCRE checks that there is a "b" later in the sub-
9854 b. The number of matched sub-patterns is >= number of supplied
10065 int a, b, c, d;
10068 pcrecpp::Octal(&a), pcrecpp::Hex(&b),
10071 will leave 64 in a, b, c, and d.
10082 pcrecpp::RE("b+").Replace("d", &s);
10092 pcrecpp::RE("b+").GlobalReplace("d", &s);
