Lines Matching refs:pcre_exec
1074 When matching with the pcre_exec() function, PCRE implements backtrack-
1098 the pcre_exec() function; it is not relevant for pcre_dfa_exec().
1105 pcre_exec() function. By controlling the maximum number of times this
1107 be placed on the resources used by a single call to pcre_exec(). The
1339 pcre_exec(), pcre16_exec() and pcre32_exec() functions. These work in
1561 int pcre_exec(const pcre *code, const pcre_extra *extra,
1698 pcre_exec() are used for compiling and matching regular expressions in
1729 string that is matched by pcre_exec(). They are:
1744 pcre_exec(), or pcre_dfa_exec(). This is an optional facility that is
1766 data, instead of recursive function calls, when running the pcre_exec()
1810 section on pcre_exec() options below.
1942 ber of internal matching function calls in a pcre_exec() execution.
1943 Further details are given with pcre_exec() below.
1949 pcre_exec() execution. Further details are given with pcre_exec()
1955 running pcre_exec() is implemented by recursive function calls that use
2030 compiled pattern, and used again by pcre_exec(), unless another table
2248 is used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.
2261 option for pcre_exec() or pcre_dfa_exec(). If it is set at compile
2302 passed to pcre_exec() and pcre_dfa_exec(), to suppress the validity
2418 pcre_exec() or pcre_dfa_exec(). However, a pcre_extra block also con-
2424 calling program wants to pass any of the other fields to pcre_exec() or
2440 faster than the pcre_exec() interpretive matching function. If the
2449 pcre_exec() interpreter. For more details, see the pcrejit documenta-
2477 rc = pcre_exec( /* see below for details of pcre_exec() options */
2498 These two optimizations apply to both pcre_exec() and pcre_dfa_exec(),
2501 calling pcre_exec() or pcre_dfa_exec(), but if this is done, JIT execu-
2536 passed to pcre_compile() or pcre_exec() as often as necessary. For
2555 and normally also by pcre_exec(). Thus, by default, for any single pat-
2560 the internal tables) to pcre_exec(). Although not intended for this
2735 pointers in the output vector (described with pcre_exec() below). To do
2786 pcre_exec(), otherwise 0. The fourth argument should point to an int
2928 int pcre_exec(const pcre *code, const pcre_extra *extra,
2932 The function pcre_exec() is called to match a subject string against a
2935 argument. You can call pcre_exec() with the same code and extra argu-
2945 ally studied) in the same process that calls pcre_exec(). However, it
2950 Here is an example of a simple call to pcre_exec():
2954 rc = pcre_exec(
2964 Extra data for pcre_exec()
3010 Internally, pcre_exec() uses a function called match(), which it calls
3017 When pcre_exec() is called with a pattern that was successfully studied
3026 cases. You can override the default by suppling pcre_exec() with a
3029 exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
3045 match_limit. You can override the default by suppling pcre_exec() with
3048 limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
3054 pcre_exec(); this overrides the value that is stored with the compiled
3057 ment. If NULL is passed to pcre_exec() using this mechanism, it forces
3061 address when pcre_exec() is called. See the pcreprecompile documenta-
3076 Option bits for pcre_exec()
3078 The unused bits of the options argument for pcre_exec() must be zero.
3089 interpretive code in pcre_exec() is run.
3093 The PCRE_ANCHORED option limits pcre_exec() to matching at the first
3195 There are a number of optimizations that pcre_exec() uses at the start
3247 UTF-8 string is automatically checked when pcre_exec() is subsequently
3252 sequence of bytes is found, pcre_exec() returns the error
3257 tled Error return values from pcre_exec() below). If startoffset con-
3263 PCRE_NO_UTF8_CHECK option when calling pcre_exec(). You might want to
3264 do this for the second and subsequent calls to pcre_exec() if you are
3287 case, if a partial match is found, pcre_exec() immediately returns
3297 The string to be matched by pcre_exec()
3299 The subject string is passed to pcre_exec() as a pointer in subject, a
3302 pcre_exec() returns PCRE_ERROR_BADOFFSET. When the starting offset is
3310 in the same subject by calling pcre_exec() again after a previous suc-
3319 When applied to the string "Mississipi" the first call to pcre_exec()
3320 finds the first occurrence. If pcre_exec() is called again with just
3323 to be a word boundary. However, if pcre_exec() is passed the entire
3344 How pcre_exec() returns captured substrings
3361 of the vector is used as workspace by pcre_exec() while matching cap-
3377 returned by pcre_exec() is one more than the highest numbered pair that
3389 nor any captured substrings are of interest, pcre_exec() may be called
3403 given with subject string "abd", pcre_exec() will try to set the second
3434 tor[0] to ovector[2n+1] are set by pcre_exec(). The other elements (in
3440 Error return values from pcre_exec()
3442 If pcre_exec() fails, it returns a negative number. The following are
3475 to pcre_exec() is not big enough to remember the referenced substrings,
3480 This error is also given if pcre_stack_malloc() fails in pcre_exec().
3488 returned by pcre_exec().
3498 This error is never generated by pcre_exec() itself. It is provided for
3569 This error is returned when pcre_exec() detects a recursion loop within
3607 This error is given if pcre_exec() is called with a negative value for
3610 Error numbers -16 to -20, -22, and 30 are not used by pcre_exec().
3618 When pcre_exec() returns either PCRE_ERROR_BADUTF8 or PCRE_ERROR_SHORT-
3708 returned by pcre_exec() in ovector. For convenience, the functions
3726 passed to pcre_exec(), and stringcount is the number of substrings that
3728 entire regular expression. This is the value returned by pcre_exec() if
3729 it is greater than zero. If pcre_exec() returned zero, indicating that
3886 rent matched substring. Then return 1, which forces pcre_exec() to
3888 matches, pcre_exec() will yield PCRE_ERROR_NOMATCH.
3893 Matching certain patterns using pcre_exec() can use a lot of process
3896 that is used by pcre_exec(), to help them set recursion limits, as
3899 ing pcre_exec with the values NULL, NULL, NULL, -999, and -999 for its
3902 Normally, if its first argument is NULL, pcre_exec() immediately
3908 pcre_exec() occur when there are one or two additional variables on the
3934 pcre_exec(), plus two extras. The ovector argument is used in a differ-
3936 used in the same way as for pcre_exec(), so their description is not
3970 four of these are exactly the same as for pcre_exec(), so their
3976 These have the same general effect as they do for pcre_exec(), but the
4033 compatibility with the way pcre_exec() returns data, even though the
4039 filled with the longest matches. Unlike pcre_exec(), pcre_dfa_exec()
4045 Many of the errors are the same as for pcre_exec(), and these are
4228 passed by the caller to the matching function. When pcre_exec() or
4247 When the pcre_exec() or pcre[16|32]_exec() is used, the capture_top
4280 callouts from pcre_exec() or pcre[16|32]_exec() it contains a pointer
4459 and PCRE_NO_AUTO_CAPTURE options for pcre_exec() have no Perl equiva-
4557 ported by PCRE when one its main matching functions, pcre_exec()
5271 However, if the startoffset argument of pcre_exec() is non-zero, indi-
5279 of pcre_exec(). It differs from \A when the value of startoffset is
5280 non-zero. By calling pcre_exec() multiple times with appropriate argu-
5304 ment of pcre_exec() is non-zero, circumflex can never match if the
5342 pcre_exec() is non-zero. The PCRE_DOLLAR_ENDONLY option is ignored if
6915 pile() or pcre_exec(), or by starting the pattern with (*NO_START_OPT).
6917 bits for pcre_exec()" in the pcreapi documentation.
6968 entitled "Extra data for pcre_exec()" in the pcreapi documentation.
7026 pcre_exec() is committed to finding a match at the current starting
7650 first byte of the failing character. The run-time functions pcre_exec()
7666 this option to pcre_exec() or pcre_dfa_exec().
7864 pcre_exec().
7889 PCRE_PARTIAL_HARD or PCRE_PARTIAL_SOFT options of pcre_exec(), you
7897 three modes (normal, soft partial, hard partial). When pcre_exec() is
7908 cutes much faster than the normal interpretive code. When pcre_exec()
7914 There are some pcre_exec() options that are not supported for JIT exe-
7939 The only pcre_exec() options that are supported for JIT execution are
7958 the same as those given by the interpretive pcre_exec() code, with the
7962 patibility with the interpretive pcre_exec() code, no more than two-
8033 is not obeyed when pcre_exec() is called with options that are incom-
8097 by pcre_exec(), (that is, it is assigned to the pattern currently run-
8106 pcre_exec() again. When you assign the stack to a pattern, only a
8109 call pcre_exec() with a pattern pointing to an already freed stack, as
8111 pcre_exec() in another thread). You can also replace the stack for a
8116 pcre_exec()?
8157 rc = pcre_exec(re, extra, subject, length, 0, 0, ovector, 30);
8169 pcre_exec() does have a performance impact. Programs that are written
8172 execution directly instead of calling pcre_exec() (obviously only for
8176 the same arguments as pcre_exec(), plus one additional argument that
8178 do not apply. The return values are the same as for pcre_exec().
8180 When you call pcre_exec(), as well as testing for invalid options, a
8188 Bypassing the sanity checks and the pcre_exec() wrapping can give
8271 PARTIAL MATCHING USING pcre_exec() OR pcre[16|32]_exec()
8273 A partial match occurs during a call to pcre_exec() or
8305 PCRE_PARTIAL_SOFT WITH pcre_exec() OR pcre[16|32]_exec()
8307 If PCRE_PARTIAL_SOFT is set when pcre_exec() or pcre[16|32]_exec()
8331 PCRE_PARTIAL_HARD WITH pcre_exec() OR pcre[16|32]_exec()
8333 If PCRE_PARTIAL_HARD is set for pcre_exec() or pcre[16|32]_exec(),
8428 optimizations were implemented in the pcre_exec() function, the
8436 not conform to the restrictions, pcre_exec() returned the error code
8500 MULTI-SEGMENT MATCHING WITH pcre_exec() OR pcre[16|32]_exec()
8863 When pcre_exec() or pcre[16|32]_exec() is used for matching, certain
