Lines Matching full:patterns
70 alternative function that matches the same compiled patterns in a dif-
110 supply arbitrary patterns for compilation, you should be aware of a
114 which interprets patterns and subjects as strings of UTF-8 characters
169 pcreprecompile details of saving and re-using precompiled patterns
364 patterns and JIT stacks are pcre16 and pcre16_jit_stack respectively.
418 patterns uses 16-bit characters. The pcre16_get_stringtable_entries()
464 patterns in the other mode, for example, if a pattern compiled with
496 with the command line option -16, patterns and subject strings are con-
695 patterns and JIT stacks are pcre32 and pcre32_jit_stack respectively.
749 patterns
793 to a function that processes patterns in the other mode, for example,
824 with the command line option -32, patterns and subject strings are con-
1085 HANDLING VERY LARGE PATTERNS
1092 but the most gigantic patterns. Nevertheless, some people do want to
1093 process truly enormous patterns, so it is possible to compile PCRE to
1752 matching performance of many patterns. Simple programs can easily
1887 SAVING PRECOMPILED PATTERNS FOR LATER USE
1982 default value of 2 is sufficient for all but the most massive patterns,
2208 patterns. Note, however, that this applies only to data characters.
2289 that process patterns from external sources. The combination of
2333 in patterns are treated as literal data.
2552 for patterns to be analyzed, and for one-off matches and simple pat-
2554 study time. Not all patterns can be optimized by the JIT compiler. For
2598 Studying a pattern is also useful for non-anchored patterns that do not
2673 but different patterns can be processed in different locales.
2678 vided for use with pre-compiled patterns that have been saved and
2679 reloaded. Character tables are not saved with patterns, so if a non-
2773 -2 is returned. For anchored patterns, -2 is returned.
2806 returned. For anchored patterns, 0 is returned.
2850 is no such value, -1 is returned. For anchored patterns, a last literal
2984 For such patterns, the PCRE_ANCHORED bit is set in the options returned
3026 For anchored patterns, a last literal value is recorded only if it fol-
3081 is possible to save compiled patterns and study data, and then use them
3140 a vast amount of resources when running patterns that are not going to
3149 take place. For patterns that are not anchored, the count restarts from
3206 The tables field is provided for use with patterns that have been pre-
3210 cussion of saving compiled patterns for later use. If NULL is passed
3737 position in the subject string. Some simple patterns that might do this
4015 Normally, patterns with duplicate names are such that in any one match,
4059 Matching certain patterns using pcre_exec() can use a lot of process
4093 Perl. Some of the features of PCRE patterns are not supported. Never-
4108 workspace will be needed for patterns and subjects where there are a
4351 piles and matches patterns, callouts sometimes do not happen exactly as
4398 patterns, if it has been scanned far enough.
4605 constructions. However, there is support for recursive patterns. This
4704 (j) Patterns compiled by PCRE can be saved and re-used at a later time,
4755 This document discusses the patterns that are supported by PCRE when
4798 Some applications that allow their users to supply patterns may wish to
4868 are provoked by patterns with huge matching trees (a typical example is
4999 acters in patterns in a visible manner. There is no restriction on the
5669 Consequently, patterns that are anchored in single line mode because
5956 from other environments, and is best not used in any new patterns. Note
5966 Vertical bar characters are used to separate alternative patterns. For
6084 between the "?" and the ":". Thus the two patterns
6092 subsequent branches, so the above patterns match "SUNDAY" as well as
6146 patterns. This feature was not added to Perl until release 5.10. Python
6169 cate names can be useful for patterns where only one instance of the
6213 patterns with the same number because PCRE uses only the numbers when
6288 for such patterns. However, because there are cases where this can be
6289 useful, such patterns are now accepted, but if any repetition of the
6530 references can be helpful in long patterns, and also in patterns that
6588 patterns. For example, the pattern
6878 syntax for recursive patterns is described below.
6923 There are two ways of including comments in patterns that are processed
6950 RECURSIVE PATTERNS
7134 WARNING: The palindrome-matching patterns above work only if the sub-
8017 CONDITIONAL PATTERNS
8144 When you set the PCRE_UTF8 flag, the byte strings passed as patterns
8189 are passed as patterns and subjects are (by default) checked for valid-
8212 are passed as patterns and subjects are (by default) checked for valid-
8234 1. Codepoints less than 256 can be specified in patterns by either
8477 SAVING AND RESTORING COMPILED PATTERNS
8495 large or complicated patterns need more than this. The error
8543 by assigning directly or by callback), as long as the patterns are all
8552 NULL stack to any number of patterns as long as they are not used for
8554 assign the same stack to all compiled patterns, and use a global mutex
8612 can free the patterns and stacks in any order, anytime. Just do not
8625 this without keeping a list of the currently JIT studied patterns.
8677 patterns that have been successfully studied by JIT).
8796 For the majority of patterns, the contents of the first and third slots
8797 will be the same. However, for patterns that contain lookbehind asser-
8877 two patterns like this:
8933 FORMERLY RESTRICTED PATTERNS
8938 used with all patterns. From release 8.00 onwards, the restrictions no
9150 5. Patterns that contain alternatives at the top level which do not all
9163 alternative. There is no problem with anchored patterns or patterns
9207 SAVING AND RE-USING PRECOMPILED PCRE PATTERNS
9210 expression patterns, it may be useful to store them in a precompiled
9218 If you save compiled patterns to a file, you can copy them to a differ-
9264 Saving compiled patterns in a file is only one possible way of storing
9320 In general, it is safest to recompile all saved patterns when you
9355 Patterns are compiled by PCRE into a reasonably efficient interpretive
9356 code, so that most simple patterns do not use much memory. However,
9383 larger compiled patterns, but it is better to try to rewrite your pat-
9386 One way of reducing the memory usage for such patterns is to make use
9399 kind of rewriting will allow you to process patterns that PCRE cannot
9416 Certain items in regular expression patterns are processed more effi-
9461 Beware of patterns that contain nested indefinite repeats. These can
9799 sub-strings that match sub-patterns into them.
9826 Example: does not try to extract any extra sub-patterns
9835 Example: fails because there aren't enough sub-patterns:
9854 b. The number of matched sub-patterns is >= number of supplied
9861 number of sub-patterns, "i"th captured sub-pattern is
10236 patterns of around 200,000. Repeated forward references with fixed
10252 the size of a subject string that can be processed by certain patterns.
10309 workspace it is given. However, it is possible to write patterns with
10310 runaway infinite recursions; such patterns will cause
