/[pcre]/code/trunk/doc/pcre.3
ViewVC logotype

Diff of /code/trunk/doc/pcre.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1220 by ph10, Sun Nov 11 18:04:37 2012 UTC revision 1221 by ph10, Sun Nov 11 20:27:03 2012 UTC
# Line 114  If you are using PCRE in a non-UTF appli Line 114  If you are using PCRE in a non-UTF appli
114  arbitrary patterns for compilation, you should be aware of a feature that  arbitrary patterns for compilation, you should be aware of a feature that
115  allows users to turn on UTF support from within a pattern, provided that PCRE  allows users to turn on UTF support from within a pattern, provided that PCRE
116  was built with UTF support. For example, an 8-bit pattern that begins with  was built with UTF support. For example, an 8-bit pattern that begins with
117  "(*UTF8)" or "(*UTF)" turns on UTF-8 mode, which interprets patterns and  "(*UTF8)" or "(*UTF)" turns on UTF-8 mode, which interprets patterns and
118  subjects as strings of UTF-8 characters instead of individual 8-bit characters.  subjects as strings of UTF-8 characters instead of individual 8-bit characters.
119  This causes both the pattern and any data against which it is matched to be  This causes both the pattern and any data against which it is matched to be
120  checked for UTF-8 validity. If the data string is very long, such a check might  checked for UTF-8 validity. If the data string is very long, such a check might
# Line 126  The best way of guarding against this po Line 126  The best way of guarding against this po
126  .P  .P
127  If your application is one that supports UTF, be aware that validity checking  If your application is one that supports UTF, be aware that validity checking
128  can take time. If the same data string is to be matched many times, you can use  can take time. If the same data string is to be matched many times, you can use
129  the PCRE_NO_UTF[8|16|32]_CHECK option for the second and subsequent matches to  the PCRE_NO_UTF[8|16|32]_CHECK option for the second and subsequent matches to
130  save redundant checks.  save redundant checks.
131  .P  .P
132  Another way that performance can be hit is by running a pattern that has a very  Another way that performance can be hit is by running a pattern that has a very
133  large search tree against a string that will never match. Nested unlimited  large search tree against a string that will never match. Nested unlimited
134  repeats in a pattern are a common example. PCRE provides some protection  repeats in a pattern are a common example. PCRE provides some protection
135  against this: see the PCRE_EXTRA_MATCH_LIMIT feature in the  against this: see the PCRE_EXTRA_MATCH_LIMIT feature in the
136  .\" HREF  .\" HREF
137  \fBpcreapi\fP  \fBpcreapi\fP

Legend:
Removed from v.1220  
changed lines
  Added in v.1221

  ViewVC Help
Powered by ViewVC 1.1.5