/[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 211 by ph10, Thu Aug 9 09:52:43 2007 UTC revision 429 by ph10, Tue Sep 1 16:10:16 2009 UTC
# Line 24  man page, in case the conversion went wr Line 24  man page, in case the conversion went wr
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. (Certain features that appeared in Python and PCRE before they  differences. Certain features that appeared in Python and PCRE before they
28  appeared in Perl are also available using the Python syntax.)  appeared in Perl are also available using the Python syntax. There is also some
29    support for certain .NET and Oniguruma syntax items, and there is an option for
30    requesting some minor changes that give better JavaScript compatibility.
31  </P>  </P>
32  <P>  <P>
33  The current implementation of PCRE (release 7.x) corresponds approximately with  The current implementation of PCRE (release 8.xx) corresponds approximately
34  Perl 5.10, including support for UTF-8 encoded strings and Unicode general  with Perl 5.10, including support for UTF-8 encoded strings and Unicode general
35  category properties. However, UTF-8 and Unicode support has to be explicitly  category properties. However, UTF-8 and Unicode support has to be explicitly
36  enabled; it is not the default. The Unicode tables correspond to Unicode  enabled; it is not the default. The Unicode tables correspond to Unicode
37  release 5.0.0.  release 5.1.
38  </P>  </P>
39  <P>  <P>
40  In addition to the Perl-compatible matching function, PCRE contains an  In addition to the Perl-compatible matching function, PCRE contains an
# Line 86  not exported. Line 88  not exported.
88  The user documentation for PCRE comprises a number of different sections. In  The user documentation for PCRE comprises a number of different sections. In
89  the "man" format, each of these is a separate "man page". In the HTML format,  the "man" format, each of these is a separate "man page". In the HTML format,
90  each is a separate page, linked from the index page. In the plain text format,  each is a separate page, linked from the index page. In the plain text format,
91  all the sections are concatenated, for ease of searching. The sections are as  all the sections, except the <b>pcredemo</b> section, are concatenated, for ease
92  follows:  of searching. The sections are as follows:
93  <pre>  <pre>
94    pcre              this document    pcre              this document
95    pcre-config       show PCRE installation configuration information    pcre-config       show PCRE installation configuration information
# Line 96  follows: Line 98  follows:
98    pcrecallout       details of the callout feature    pcrecallout       details of the callout feature
99    pcrecompat        discussion of Perl compatibility    pcrecompat        discussion of Perl compatibility
100    pcrecpp           details of the C++ wrapper    pcrecpp           details of the C++ wrapper
101      pcredemo          a demonstration C program that uses PCRE
102    pcregrep          description of the <b>pcregrep</b> command    pcregrep          description of the <b>pcregrep</b> command
103    pcrematching      discussion of the two matching algorithms    pcrematching      discussion of the two matching algorithms
104    pcrepartial       details of the partial matching facility    pcrepartial       details of the partial matching facility
# Line 104  follows: Line 107  follows:
107    pcreperform       discussion of performance issues    pcreperform       discussion of performance issues
108    pcreposix         the POSIX-compatible C API    pcreposix         the POSIX-compatible C API
109    pcreprecompile    details of saving and re-using precompiled patterns    pcreprecompile    details of saving and re-using precompiled patterns
110    pcresample        discussion of the sample program    pcresample        discussion of the pcredemo program
111    pcrestack         discussion of stack usage    pcrestack         discussion of stack usage
112    pcretest          description of the <b>pcretest</b> testing command    pcretest          description of the <b>pcretest</b> testing command
113  </pre>  </pre>
# Line 158  category properties was added. Line 161  category properties was added.
161  In order process UTF-8 strings, you must build PCRE to include UTF-8 support in  In order process UTF-8 strings, you must build PCRE to include UTF-8 support in
162  the code, and, in addition, you must call  the code, and, in addition, you must call
163  <a href="pcre_compile.html"><b>pcre_compile()</b></a>  <a href="pcre_compile.html"><b>pcre_compile()</b></a>
164  with the PCRE_UTF8 option flag. When you do this, both the pattern and any  with the PCRE_UTF8 option flag, or the pattern must start with the sequence
165  subject strings that are matched against it are treated as UTF-8 strings  (*UTF8). When either of these is the case, both the pattern and any subject
166  instead of just strings of bytes.  strings that are matched against it are treated as UTF-8 strings instead of
167    just strings of bytes.
168  </P>  </P>
169  <P>  <P>
170  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
# Line 256  digits, spaces, or word characters remai Line 260  digits, spaces, or word characters remai
260  values less than 256. This remains true even when PCRE includes Unicode  values less than 256. This remains true even when PCRE includes Unicode
261  property support, because to do otherwise would slow down PCRE in many common  property support, because to do otherwise would slow down PCRE in many common
262  cases. If you really want to test for a wider sense of, say, "digit", you  cases. If you really want to test for a wider sense of, say, "digit", you
263  must use Unicode property tests such as \p{Nd}.  must use Unicode property tests such as \p{Nd}. Note that this also applies to
264    \b, because it is defined in terms of \w and \W.
265  </P>  </P>
266  <P>  <P>
267  7. Similarly, characters that match the POSIX named character classes are all  7. Similarly, characters that match the POSIX named character classes are all
# Line 293  two digits 10, at the domain cam.ac.uk. Line 298  two digits 10, at the domain cam.ac.uk.
298  </P>  </P>
299  <br><a name="SEC6" href="#TOC1">REVISION</a><br>  <br><a name="SEC6" href="#TOC1">REVISION</a><br>
300  <P>  <P>
301  Last updated: 09 August 2007  Last updated: 01 September 2009
302  <br>  <br>
303  Copyright &copy; 1997-2007 University of Cambridge.  Copyright &copy; 1997-2009 University of Cambridge.
304  <br>  <br>
305  <p>  <p>
306  Return to the <a href="index.html">PCRE index page</a>.  Return to the <a href="index.html">PCRE index page</a>.

Legend:
Removed from v.211  
changed lines
  Added in v.429

  ViewVC Help
Powered by ViewVC 1.1.5