Lines Matching refs:pcre_exec
1108 When matching with the pcre_exec() function, PCRE implements backtrack-
1132 the pcre_exec() function; it is not relevant for pcre_dfa_exec().
1139 pcre_exec() function. By controlling the maximum number of times this
1141 be placed on the resources used by a single call to pcre_exec(). The
1373 pcre_exec(), pcre16_exec() and pcre32_exec() functions. These work in
1605 int pcre_exec(const pcre *code, const pcre_extra *extra,
1743 pcre_exec() are used for compiling and matching regular expressions in
1774 string that is matched by pcre_exec(). They are:
1789 pcre_exec(), or pcre_dfa_exec(). This is an optional facility that is
1811 data, instead of recursive function calls, when running the pcre_exec()
1863 section on pcre_exec() options below.
2006 ber of internal matching function calls in a pcre_exec() execution.
2007 Further details are given with pcre_exec() below.
2013 pcre_exec() execution. Further details are given with pcre_exec()
2019 running pcre_exec() is implemented by recursive function calls that use
2096 compiled pattern, and used again by pcre_exec() and pcre_dfa_exec()
2336 is used for pcre_exec() and pcre_dfa_exec(), but it can be overridden.
2359 option for pcre_exec() or pcre_dfa_exec(). If it is set at compile
2401 be passed to pcre_exec() and pcre_dfa_exec(), to suppress the validity
2525 pcre_exec() or pcre_dfa_exec(). However, a pcre_extra block also con-
2531 calling program wants to pass any of the other fields to pcre_exec() or
2547 faster than the pcre_exec() interpretive matching function. If the
2556 pcre_exec() interpreter. For more details, see the pcrejit documenta-
2584 rc = pcre_exec( /* see below for details of pcre_exec() options */
2605 These two optimizations apply to both pcre_exec() and pcre_dfa_exec(),
2614 pcre_exec(), (that is, after any JIT compilation has happened) JIT exe-
2671 and also by pcre_exec() and pcre_dfa_exec(). Thus, for any single pat-
2676 the internal tables) to pcre_exec() or pcre_dfa_exec() (see the discus-
2906 pointers in the output vector (described with pcre_exec() below). To do
2958 pcre_exec(), otherwise 0. The fourth argument should point to an int
3063 int pcre_exec(const pcre *code, const pcre_extra *extra,
3067 The function pcre_exec() is called to match a subject string against a
3070 argument. You can call pcre_exec() with the same code and extra argu-
3080 ally studied) in the same process that calls pcre_exec(). However, it
3085 Here is an example of a simple call to pcre_exec():
3089 rc = pcre_exec(
3099 Extra data for pcre_exec()
3145 Internally, pcre_exec() uses a function called match(), which it calls
3152 When pcre_exec() is called with a pattern that was successfully studied
3161 cases. You can override the default by suppling pcre_exec() with a
3164 exceeded, pcre_exec() returns PCRE_ERROR_MATCHLIMIT.
3172 d is less than the limit set by the caller of pcre_exec() or, if no
3189 match_limit. You can override the default by suppling pcre_exec() with
3192 limit is exceeded, pcre_exec() returns PCRE_ERROR_RECURSIONLIMIT.
3200 d is less than the limit set by the caller of pcre_exec() or, if no
3213 Warning: The tables that pcre_exec() uses must be the same as those
3215 the behaviour of pcre_exec() is undefined. Therefore, when a pattern is
3219 pcre_exec().
3233 Option bits for pcre_exec()
3235 The unused bits of the options argument for pcre_exec() must be zero.
3246 interpretive code in pcre_exec() is run.
3250 The PCRE_ANCHORED option limits pcre_exec() to matching at the first
3352 There are a number of optimizations that pcre_exec() uses at the start
3371 pcre_exec()) disables JIT execution; in this situation, matching is
3405 UTF-8 string is automatically checked when pcre_exec() is subsequently
3410 sequence of bytes is found, pcre_exec() returns the error
3415 tled Error return values from pcre_exec() below). If startoffset con-
3421 PCRE_NO_UTF8_CHECK option when calling pcre_exec(). You might want to
3422 do this for the second and subsequent calls to pcre_exec() if you are
3445 case, if a partial match is found, pcre_exec() immediately returns
3455 The string to be matched by pcre_exec()
3457 The subject string is passed to pcre_exec() as a pointer in subject, a
3464 pcre_exec() returns PCRE_ERROR_BADOFFSET. When the starting offset is
3473 in the same subject by calling pcre_exec() again after a previous suc-
3482 When applied to the string "Mississipi" the first call to pcre_exec()
3483 finds the first occurrence. If pcre_exec() is called again with just
3486 to be a word boundary. However, if pcre_exec() is passed the entire
3507 How pcre_exec() returns captured substrings
3524 of the vector is used as workspace by pcre_exec() while matching cap-
3542 returned by pcre_exec() is one more than the highest numbered pair that
3554 nor any captured substrings are of interest, pcre_exec() may be called
3568 given with subject string "abd", pcre_exec() will try to set the second
3599 tor[0] to ovector[2n+1] are set by pcre_exec(). The other elements (in
3605 Error return values from pcre_exec()
3607 If pcre_exec() fails, it returns a negative number. The following are
3640 to pcre_exec() is not big enough to remember the referenced substrings,
3645 This error is also given if pcre_stack_malloc() fails in pcre_exec().
3653 returned by pcre_exec().
3663 This error is never generated by pcre_exec() itself. It is provided for
3734 This error is returned when pcre_exec() detects a recursion loop within
3772 This error is given if pcre_exec() is called with a negative value for
3775 Error numbers -16 to -20, -22, and 30 are not used by pcre_exec().
3783 When pcre_exec() returns either PCRE_ERROR_BADUTF8 or PCRE_ERROR_SHORT-
3874 returned by pcre_exec() in ovector. For convenience, the functions
3892 passed to pcre_exec(), and stringcount is the number of substrings that
3894 entire regular expression. This is the value returned by pcre_exec() if
3895 it is greater than zero. If pcre_exec() returned zero, indicating that
4052 rent matched substring. Then return 1, which forces pcre_exec() to
4054 matches, pcre_exec() will yield PCRE_ERROR_NOMATCH.
4059 Matching certain patterns using pcre_exec() can use a lot of process
4062 that is used by pcre_exec(), to help them set recursion limits, as
4065 ing pcre_exec with the values NULL, NULL, NULL, -999, and -999 for its
4068 Normally, if its first argument is NULL, pcre_exec() immediately
4074 pcre_exec() occur when there are one or two additional variables on the
4100 pcre_exec(), plus two extras. The ovector argument is used in a differ-
4102 used in the same way as for pcre_exec(), so their description is not
4136 four of these are exactly the same as for pcre_exec(), so their
4142 These have the same general effect as they do for pcre_exec(), but the
4199 compatibility with the way pcre_exec() returns data, even though the
4205 filled with the longest matches. Unlike pcre_exec(), pcre_dfa_exec()
4220 Many of the errors are the same as for pcre_exec(), and these are
4443 passed by the caller to the matching function. When pcre_exec() or
4462 When the pcre_exec() or pcre[16|32]_exec() is used, the capture_top
4498 callouts from pcre_exec() or pcre[16|32]_exec() it contains a pointer
4694 and PCRE_NO_AUTO_CAPTURE options for pcre_exec() have no Perl equiva-
4756 one its main matching functions, pcre_exec() (8-bit) or
4865 The caller of pcre_exec() can set a limit on the number of times the
4871 reached, pcre_exec() gives an error return. The limits can also be set
4879 pcre_exec() for it to have any effect. In other words, the pattern
5601 However, if the startoffset argument of pcre_exec() is non-zero, indi-
5609 of pcre_exec(). It differs from \A when the value of startoffset is
5610 non-zero. By calling pcre_exec() multiple times with appropriate argu-
5634 ment of pcre_exec() is non-zero, circumflex can never match if the
5672 pcre_exec() is non-zero. The PCRE_DOLLAR_ENDONLY option is ignored if
7311 pile() or pcre_exec(), or by starting the pattern with (*NO_START_OPT).
7313 bits for pcre_exec()" in the pcreapi documentation.
7369 pcre_exec()" in the pcreapi documentation. Here is an example of
7432 has been passed pcre_exec() is committed to finding a match at the cur-
7462 pcre_exec() is called. This disables the optimization that skips along
7952 the limits set by the caller of pcre_exec(), not increase them.
8165 first byte of the failing character. The run-time functions pcre_exec()
8181 this option to pcre_exec() or pcre_dfa_exec().
8374 pcre_exec().
8399 PCRE_PARTIAL_HARD or PCRE_PARTIAL_SOFT options of pcre_exec(), you
8407 three modes (normal, soft partial, hard partial). When pcre_exec() is
8418 cutes much faster than the normal interpretive code. When pcre_exec()
8424 There are some pcre_exec() options that are not supported for JIT exe-
8449 The only pcre_exec() options that are supported for JIT execution are
8462 the same as those given by the interpretive pcre_exec() code, with the
8466 patibility with the interpretive pcre_exec() code, no more than two-
8537 is not obeyed when pcre_exec() is called with options that are incom-
8601 by pcre_exec(), (that is, it is assigned to the pattern currently run-
8610 pcre_exec() again. When you assign the stack to a pattern, only a
8613 call pcre_exec() with a pattern pointing to an already freed stack, as
8615 pcre_exec() in another thread). You can also replace the stack for a
8620 pcre_exec()?
8661 rc = pcre_exec(re, extra, subject, length, 0, 0, ovector, 30);
8673 pcre_exec() does have a performance impact. Programs that are written
8676 execution directly instead of calling pcre_exec() (obviously only for
8680 the same arguments as pcre_exec(), plus one additional argument that
8682 do not apply. The return values are the same as for pcre_exec().
8684 When you call pcre_exec(), as well as testing for invalid options, a
8692 Bypassing the sanity checks and the pcre_exec() wrapping can give
8775 PARTIAL MATCHING USING pcre_exec() OR pcre[16|32]_exec()
8777 A partial match occurs during a call to pcre_exec() or
8813 PCRE_PARTIAL_SOFT WITH pcre_exec() OR pcre[16|32]_exec()
8815 If PCRE_PARTIAL_SOFT is set when pcre_exec() or pcre[16|32]_exec()
8839 PCRE_PARTIAL_HARD WITH pcre_exec() OR pcre[16|32]_exec()
8841 If PCRE_PARTIAL_HARD is set for pcre_exec() or pcre[16|32]_exec(),
8936 optimizations were implemented in the pcre_exec() function, the
8944 not conform to the restrictions, pcre_exec() returned the error code
9018 MULTI-SEGMENT MATCHING WITH pcre_exec() OR pcre[16|32]_exec()
9077 argument of pcre_exec() or pcre_dfa_exec().
9299 Warning: The tables that pcre_exec() and pcre_dfa_exec() use must be
9405 When pcre_exec() or pcre[16|32]_exec() is used for matching, certain