Lines Matching refs:so
187 so I've taken it away. If you want to email me, use my two initials,
329 tern that was compiled with pcre16_compile(), you must do so with
661 must do so with pcre32_study(), not pcre_study(), and you must free the
903 works, --enable and --disable always come in pairs, so the complemen-
1064 the default is changed so that \R matches only CR, LF, or CRLF. What-
1093 process truly enormous patterns, so it is possible to compile PCRE to
1124 can replace the pointers so that your own functions are used instead.
1180 have to do so "by hand".)
1215 By default, pcregrep reads all files as plain text. You can build it so
1252 Note that libreadline is GPL-licensed, so if you distribute a binary of
1266 If your environment has not been set up so that an appropriate library
1302 before running make to build PCRE, so that ccache is not used.
1805 so a calling program can replace them if it wishes to intercept the
1815 management, it runs more slowly. Separate functions are provided so
1830 stack. This function is provided so that applications with restricted
1878 ing, so the same compiled pattern can safely be used by several threads
2144 less than 128, so caseless matching is always possible. For characters
2191 at release 5.18, so PCRE followed at release 8.34, and VT is now
2233 If this option is set, PCRE's behaviour is changed in some ways so that
2259 always expected after \x, but it may have zero, one, or two digits (so,
2329 characters, and so are ignored in this mode. Also, an unescaped # out-
2377 This option inverts the "greediness" of the quantifiers so that they
2678 reloaded. Character tables are not saved with patterns, so if a non-
2935 set, so white space - including newlines - is ignored):
2940 There are four named subpatterns, so the table has four entries, and
3014 option so that it can be saved and restored (see the pcreprecompile
3154 that goes on for a very long time, and so the match_limit value is also
3287 tains an explicit CR or LF reference, and so advances only by one char-
3302 the beginning of a line, so the circumflex metacharacter should not
3310 of a line, so the dollar metacharacter should not match it nor (except
3327 match is not valid, so PCRE searches further into the string for occur-
3346 and if so, and the current character is CR followed by LF, advance the
3386 (*COMMIT) prevents any further matches being tried, so the overall
3397 and so the (*MARK) is never encountered. In this case, studying the
3467 ject (in UTF-32 mode, one data unit equals one character, so all off-
3497 if the newline convention recognizes CRLF as a newline, and if so, and
3540 pair is used for the first capturing subpattern, and so on. The value
3758 so that it runs on the new host.
3826 so are excluded from UTF-8.
3853 This error code was formerly used when the presence of a so-called
3855 that such characters should not cause a string to be rejected, and so
4071 tive number is used so that it is clear that no match has happened.)
4101 used in the same way as for pcre_exec(), so their description is not
4135 four of these are exactly the same as for pcre_exec(), so their
4168 vector as before because data about the match so far is left in them
4444 extract substrings that have been matched so far, in the same way as
4463 tured substring so far. If no substrings have been captured, the value
4475 function specifically so that it can be passed back in callouts. It is
4658 als. PCRE has no warning features, so it gives an error in these cases
4905 the concept of case for characters whose values are less than 128, so
4960 character would otherwise be interpreted as a metacharacter, so it is
4976 ters, you can do so by putting them between \Q and \E. This is differ-
5132 Invalid Unicode codepoints are the range 0xd800 to 0xdfff (the so-
5225 PCRE_UCP option is set, the behaviour is changed so that Unicode prop-
5321 an unrecognized escape sequence, and so matches the letter "R" by
5341 does not match any characters, so always causes a match failure.
5440 so cannot be tested by PCRE, unless UTF validity checking has been
5461 do so by setting the PCRE_UCP option or by starting the pattern with
5524 tical tab, for Perl compatibility, but Perl changed, and so PCRE fol-
5654 The meaning of dollar can be changed so that it matches only at the
5779 their upper case and lower case versions, so for example, a caseless
5783 than 128, so caseless matching is always possible. For characters with
5807 two characters ("W" and "-") followed by a literal string "46]", so it
5809 backslash it is interpreted as the end of range, so [W-\]46] is inter-
5907 to pcre_compile(), some of the classes are changed so that Unicode
6006 subpattern that follows it, so
6088 subsequent branches, so the above patterns match "SUNDAY" as well as
6307 be greedy, and instead matches the minimum number of times possible, so
6336 tried against every character position in the subject string, so there
6396 \d+ item, and then with 4, and so on, before ultimately failing.
6446 edition of his book. Mike McCloskey liked it, so implemented it when he
6475 in the string.) If the pattern is changed so that it uses an atomic
6582 fails when the subpattern is first used, so, for example, (a\1) never
6671 always matches, so an assertion that requires there not to be an empty
6740 last character, then all but the last two characters, and so on. Once
6742 so we are no better off. However, if the pattern is written as
6821 most recent by (?(-2), and so on. Inside loops it can also make sense
6823 referenced as (?(+1), and so on. (The value zero in any of these forms
6837 started with an opening parenthesis, the condition is true, and so the
6950 stage, so it does not terminate the comment. Only an actual character
6951 with the code value 0x0a (the default newline) does so.
6987 PCRE_EXTENDED option is set so that white space is ignored):
6999 the entire pattern, so instead you could use this:
7029 nested unlimited repeats, and so the use of a possessive quantifier for
7038 so many different ways the + and * repeats can carve up the subject,
7098 and so the entire match fails. (Perl is able, at this point, to re-
7112 To change the pattern so that it matches all palindromic strings, not
7136 Perl takes so long that you think it has gone into a loop.
7144 natives, so the entire match fails.
7158 the recursion, \1 does now match "b" and so the whole match succeeds.
7196 tern is defined, so if it is used as a subroutine, such options cannot
7336 If (*ACCEPT) is inside capturing parentheses, the data so far is cap-
7442 of dynamic anchor, or "I've started, so I must finish." The name of the
7447 one that follows (*COMMIT) may be triggered first, so merely passing
7461 For this pattern, PCRE knows that any match must start with "a", so the
7468 so the (*COMMIT) causes the match to fail without trying any other
7533 quently BAZ fails, there are no more alternatives, so there is a back-
7575 part of the single alternative that comprises the whole pattern, and so
8050 so only if the pattern is not anchored.
8128 is limited to testing the PCRE_UTF[8|16|32] flag occasionally, so
8156 ing the surrogate area. (From release 8.33 the so-called "non-charac-
8259 will not succeed, and so the matching will be carried out by the normal
8272 character escapes work is changed so that Unicode properties are used
8396 so that no option is passed to pcre_study(), and then use something
8568 stack, this must be a different stack for each thread so that the
8600 PCRE (and JIT) is a recursive, depth-first engine, so it needs a stack
8611 ory pages inside this address space, so the stack could grow without
8784 that what has been typed so far is potentially valid, it is able to
8839 to the end of the subject so that a substring can easily be identified.
8881 matching, so PCRE_ERROR_PARTIAL is returned. The offsets are set to 3
8894 data, and so, if \z, \Z, \b, \B, or $ are encountered at the end of the
8959 "dogsbody", and so return that when PCRE_PARTIAL_HARD is set.
8972 following character cannot take place, so a partial match is found.
8974 subject when the last character is a letter, so a complete match is
9016 The first data string is matched completely, so pcretest shows the
9087 each call, so more memory and more processing time is needed.
9130 maximum lookbehind for that pattern is 3, so taking that away from 5
9361 optimization, that data cannot be saved, and so is lost by a
9403 code, so that most simple patterns do not use much memory. However,
9415 (Technical aside: It is done this way so that backtrack points within
9589 called pcreposix.a, so can be accessed by adding -lpcreposix to the
9937 meaning in a regular expression -- so this function does that. (This
9965 flag, so always use it when matching UTF8 text. For example, "." will
10093 advance "input" so it points past the matched text.
10226 ld.so.1: a.out: fatal: libpcre.so.0: open failed: No such file or
10328 pattern, in order to remember the state of the match so that it can
10380 occurs, so this formulation uses a stack frame for each matched charac-
