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

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

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

revision 83 by nigel, Sat Feb 24 21:41:06 2007 UTC revision 153 by ph10, Wed Apr 18 09:12:14 2007 UTC
# Line 18  man page, in case the conversion went wr Line 18  man page, in case the conversion went wr
18  <li><a name="TOC3" href="#SEC3">LIMITATIONS</a>  <li><a name="TOC3" href="#SEC3">LIMITATIONS</a>
19  <li><a name="TOC4" href="#SEC4">UTF-8 AND UNICODE PROPERTY SUPPORT</a>  <li><a name="TOC4" href="#SEC4">UTF-8 AND UNICODE PROPERTY SUPPORT</a>
20  <li><a name="TOC5" href="#SEC5">AUTHOR</a>  <li><a name="TOC5" href="#SEC5">AUTHOR</a>
21    <li><a name="TOC6" href="#SEC6">REVISION</a>
22  </ul>  </ul>
23  <br><a name="SEC1" href="#TOC1">INTRODUCTION</a><br>  <br><a name="SEC1" href="#TOC1">INTRODUCTION</a><br>
24  <P>  <P>
25  The PCRE library is a set of functions that implement regular expression  The PCRE library is a set of functions that implement regular expression
26  pattern matching using the same syntax and semantics as Perl, with just a few  pattern matching using the same syntax and semantics as Perl, with just a few
27  differences. The current implementation of PCRE (release 6.x) corresponds  differences. (Certain features that appeared in Python and PCRE before they
28  approximately with Perl 5.8, including support for UTF-8 encoded strings and  appeared in Perl are also available using the Python syntax.)
 Unicode general category properties. However, this support has to be explicitly  
 enabled; it is not the default.  
29  </P>  </P>
30  <P>  <P>
31  In addition to the Perl-compatible matching function, PCRE also contains an  The current implementation of PCRE (release 7.x) corresponds approximately with
32    Perl 5.10, including support for UTF-8 encoded strings and Unicode general
33    category properties. However, UTF-8 and Unicode support has to be explicitly
34    enabled; it is not the default. The Unicode tables correspond to Unicode
35    release 5.0.0.
36    </P>
37    <P>
38    In addition to the Perl-compatible matching function, PCRE contains an
39  alternative matching function that matches the same compiled patterns in a  alternative matching function that matches the same compiled patterns in a
40  different way. In certain circumstances, the alternative function has some  different way. In certain circumstances, the alternative function has some
41  advantages. For a discussion of the two matching algorithms, see the  advantages. For a discussion of the two matching algorithms, see the
# Line 82  all the sections are concatenated, for e Line 88  all the sections are concatenated, for e
88  follows:  follows:
89  <pre>  <pre>
90    pcre              this document    pcre              this document
91      pcre-config       show PCRE installation configuration information
92    pcreapi           details of PCRE's native C API    pcreapi           details of PCRE's native C API
93    pcrebuild         options for building PCRE    pcrebuild         options for building PCRE
94    pcrecallout       details of the callout feature    pcrecallout       details of the callout feature
# Line 95  follows: Line 102  follows:
102    pcreposix         the POSIX-compatible C API    pcreposix         the POSIX-compatible C API
103    pcreprecompile    details of saving and re-using precompiled patterns    pcreprecompile    details of saving and re-using precompiled patterns
104    pcresample        discussion of the sample program    pcresample        discussion of the sample program
105      pcrestack         discussion of stack usage
106    pcretest          description of the <b>pcretest</b> testing command    pcretest          description of the <b>pcretest</b> testing command
107  </pre>  </pre>
108  In addition, in the "man" and HTML formats, there is a short page for each  In addition, in the "man" and HTML formats, there is a short page for each
# Line 113  internal linkage size of 3 or 4 (see the Line 121  internal linkage size of 3 or 4 (see the
121  distribution and the  distribution and the
122  <a href="pcrebuild.html"><b>pcrebuild</b></a>  <a href="pcrebuild.html"><b>pcrebuild</b></a>
123  documentation for details). In these cases the limit is substantially larger.  documentation for details). In these cases the limit is substantially larger.
124  However, the speed of execution will be slower.  However, the speed of execution is slower.
125    </P>
126    <P>
127    All values in repeating quantifiers must be less than 65536. The maximum
128    compiled length of subpattern with an explicit repeat count is 30000 bytes. The
129    maximum number of capturing subpatterns is 65535.
130  </P>  </P>
131  <P>  <P>
132  All values in repeating quantifiers must be less than 65536.  There is no limit to the number of parenthesized subpatterns, but there can be
133  The maximum number of capturing subpatterns is 65535.  no more than 65535 capturing subpatterns.
134  </P>  </P>
135  <P>  <P>
136  There is no limit to the number of non-capturing subpatterns, but the maximum  The maximum length of name for a named subpattern is 32 characters, and the
137  depth of nesting of all kinds of parenthesized subpattern, including capturing  maximum number of named subpatterns is 10000.
 subpatterns, assertions, and other types of subpattern, is 200.  
138  </P>  </P>
139  <P>  <P>
140  The maximum length of a subject string is the largest positive number that an  The maximum length of a subject string is the largest positive number that an
141  integer variable can hold. However, when using the traditional matching  integer variable can hold. However, when using the traditional matching
142  function, PCRE uses recursion to handle subpatterns and indefinite repetition.  function, PCRE uses recursion to handle subpatterns and indefinite repetition.
143  This means that the available stack space may limit the size of a subject  This means that the available stack space may limit the size of a subject
144  string that can be processed by certain patterns.  string that can be processed by certain patterns. For a discussion of stack
145    issues, see the
146    <a href="pcrestack.html"><b>pcrestack</b></a>
147    documentation.
148  <a name="utf8support"></a></P>  <a name="utf8support"></a></P>
149  <br><a name="SEC4" href="#TOC1">UTF-8 AND UNICODE PROPERTY SUPPORT</a><br>  <br><a name="SEC4" href="#TOC1">UTF-8 AND UNICODE PROPERTY SUPPORT</a><br>
150  <P>  <P>
# Line 149  instead of just strings of bytes. Line 164  instead of just strings of bytes.
164  <P>  <P>
165  If you compile PCRE with UTF-8 support, but do not use it at run time, the  If you compile PCRE with UTF-8 support, but do not use it at run time, the
166  library will be a bit bigger, but the additional run time overhead is limited  library will be a bit bigger, but the additional run time overhead is limited
167  to testing the PCRE_UTF8 flag in several places, so should not be very large.  to testing the PCRE_UTF8 flag occasionally, so should not be very big.
168  </P>  </P>
169  <P>  <P>
170  If PCRE is built with Unicode character property support (which implies UTF-8  If PCRE is built with Unicode character property support (which implies UTF-8
171  support), the escape sequences \p{..}, \P{..}, and \X are supported.  support), the escape sequences \p{..}, \P{..}, and \X are supported.
172  The available properties that can be tested are limited to the general  The available properties that can be tested are limited to the general
173  category properties such as Lu for an upper case letter or Nd for a decimal  category properties such as Lu for an upper case letter or Nd for a decimal
174  number. A full list is given in the  number, the Unicode script names such as Arabic or Han, and the derived
175    properties Any and L&. A full list is given in the
176  <a href="pcrepattern.html"><b>pcrepattern</b></a>  <a href="pcrepattern.html"><b>pcrepattern</b></a>
177  documentation. The PCRE library is increased in size by about 90K when Unicode  documentation. Only the short names for properties are supported. For example,
178  property support is included.  \p{L} matches a letter. Its Perl synonym, \p{Letter}, is not supported.
179    Furthermore, in Perl, many properties may optionally be prefixed by "Is", for
180    compatibility with Perl 5.6. PCRE does not support this.
181  </P>  </P>
182  <P>  <P>
183  The following comments apply when PCRE is running in UTF-8 mode:  The following comments apply when PCRE is running in UTF-8 mode:
# Line 177  PCRE when PCRE_NO_UTF8_CHECK is set, the Line 195  PCRE when PCRE_NO_UTF8_CHECK is set, the
195  may crash.  may crash.
196  </P>  </P>
197  <P>  <P>
198  2. In a pattern, the escape sequence \x{...}, where the contents of the braces  2. An unbraced hexadecimal escape sequence (such as \xb3) matches a two-byte
199  is a string of hexadecimal digits, is interpreted as a UTF-8 character whose  UTF-8 character if the value is greater than 127.
 code number is the given hexadecimal number, for example: \x{1234}. If a  
 non-hexadecimal digit appears between the braces, the item is not recognized.  
 This escape sequence can be used either as a literal, or within a character  
 class.  
200  </P>  </P>
201  <P>  <P>
202  3. The original hexadecimal escape sequence, \xhh, matches a two-byte UTF-8  3. Octal numbers up to \777 are recognized, and match two-byte UTF-8
203  character if the value is greater than 127.  characters for values greater than \177.
204  </P>  </P>
205  <P>  <P>
206  4. Repeat quantifiers apply to complete UTF-8 characters, not to individual  4. Repeat quantifiers apply to complete UTF-8 characters, not to individual
# Line 219  than 128, unless PCRE is built with Unic Line 233  than 128, unless PCRE is built with Unic
233  property support is available, PCRE still uses its own character tables when  property support is available, PCRE still uses its own character tables when
234  checking the case of low-valued characters, so as not to degrade performance.  checking the case of low-valued characters, so as not to degrade performance.
235  The Unicode property information is used only for characters with higher  The Unicode property information is used only for characters with higher
236  values.  values. Even when Unicode property support is available, PCRE supports
237    case-insensitive matching only when there is a one-to-one mapping between a
238    letter's cases. There are a small number of many-to-one mappings in Unicode;
239    these are not supported by PCRE.
240  </P>  </P>
241  <br><a name="SEC5" href="#TOC1">AUTHOR</a><br>  <br><a name="SEC5" href="#TOC1">AUTHOR</a><br>
242  <P>  <P>
243  Philip Hazel  Philip Hazel
244  <br>  <br>
245  University Computing Service,  University Computing Service
246    <br>
247    Cambridge CB2 3QH, England.
248  <br>  <br>
 Cambridge CB2 3QG, England.  
249  </P>  </P>
250  <P>  <P>
251  Putting an actual email address here seems to have been a spam magnet, so I've  Putting an actual email address here seems to have been a spam magnet, so I've
252  taken it away. If you want to email me, use my initial and surname, separated  taken it away. If you want to email me, use my two initials, followed by the
253  by a dot, at the domain ucs.cam.ac.uk.  two digits 10, at the domain cam.ac.uk.
254  Last updated: 07 March 2005  </P>
255    <br><a name="SEC6" href="#TOC1">REVISION</a><br>
256    <P>
257    Last updated: 18 April 2007
258    <br>
259    Copyright &copy; 1997-2007 University of Cambridge.
260  <br>  <br>
 Copyright &copy; 1997-2005 University of Cambridge.  
261  <p>  <p>
262  Return to the <a href="index.html">PCRE index page</a>.  Return to the <a href="index.html">PCRE index page</a>.
263  </p>  </p>

Legend:
Removed from v.83  
changed lines
  Added in v.153

  ViewVC Help
Powered by ViewVC 1.1.5