Load pcre-6.3 into code/trunk.

git-svn-id: svn://vcs.exim.org/pcre/code/trunk@83 2f5784b3-3f2a-0410-8824-cb99058d5e15

1 files changed, 30 insertions, 19 deletions

diff --git a/doc/html/pcrebuild.html b/doc/html/pcrebuild.html
index 4f9ff8b..06b1e2e 100644
--- a/doc/html/pcrebuild.html
+++ b/doc/html/pcrebuild.html
@@ -14,15 +14,16 @@ man page, in case the conversion went wrong.
 <br>
 <ul>
 <li><a name="TOC1" href="#SEC1">PCRE BUILD-TIME OPTIONS</a>
-<li><a name="TOC2" href="#SEC2">UTF-8 SUPPORT</a>
-<li><a name="TOC3" href="#SEC3">UNICODE CHARACTER PROPERTY SUPPORT</a>
-<li><a name="TOC4" href="#SEC4">CODE VALUE OF NEWLINE</a>
-<li><a name="TOC5" href="#SEC5">BUILDING SHARED AND STATIC LIBRARIES</a>
-<li><a name="TOC6" href="#SEC6">POSIX MALLOC USAGE</a>
-<li><a name="TOC7" href="#SEC7">LIMITING PCRE RESOURCE USAGE</a>
-<li><a name="TOC8" href="#SEC8">HANDLING VERY LARGE PATTERNS</a>
-<li><a name="TOC9" href="#SEC9">AVOIDING EXCESSIVE STACK USAGE</a>
-<li><a name="TOC10" href="#SEC10">USING EBCDIC CODE</a>
+<li><a name="TOC2" href="#SEC2">C++ SUPPORT</a>
+<li><a name="TOC3" href="#SEC3">UTF-8 SUPPORT</a>
+<li><a name="TOC4" href="#SEC4">UNICODE CHARACTER PROPERTY SUPPORT</a>
+<li><a name="TOC5" href="#SEC5">CODE VALUE OF NEWLINE</a>
+<li><a name="TOC6" href="#SEC6">BUILDING SHARED AND STATIC LIBRARIES</a>
+<li><a name="TOC7" href="#SEC7">POSIX MALLOC USAGE</a>
+<li><a name="TOC8" href="#SEC8">LIMITING PCRE RESOURCE USAGE</a>
+<li><a name="TOC9" href="#SEC9">HANDLING VERY LARGE PATTERNS</a>
+<li><a name="TOC10" href="#SEC10">AVOIDING EXCESSIVE STACK USAGE</a>
+<li><a name="TOC11" href="#SEC11">USING EBCDIC CODE</a>
 </ul>
 <br><a name="SEC1" href="#TOC1">PCRE BUILD-TIME OPTIONS</a><br>
 <P>
@@ -41,7 +42,17 @@ or --disable. These settings specify changes to the defaults for the
 --enable and --disable always come in pairs, so the complementary option always
 exists as well, but as it specifies the default, it is not described.
 </P>
-<br><a name="SEC2" href="#TOC1">UTF-8 SUPPORT</a><br>
+<br><a name="SEC2" href="#TOC1">C++ SUPPORT</a><br>
+<P>
+By default, the <b>configure</b> script will search for a C++ compiler and C++
+header files. If it finds them, it automatically builds the C++ wrapper library
+for PCRE. You can disable this by adding
+<pre>
+  --disable-cpp
+</pre>
+to the <b>configure</b> command.
+</P>
+<br><a name="SEC3" href="#TOC1">UTF-8 SUPPORT</a><br>
 <P>
 To build PCRE with support for UTF-8 character strings, add
 <pre>
@@ -52,7 +63,7 @@ strings as UTF-8. As well as compiling PCRE with this option, you also have
 have to set the PCRE_UTF8 option when you call the <b>pcre_compile()</b>
 function.
 </P>
-<br><a name="SEC3" href="#TOC1">UNICODE CHARACTER PROPERTY SUPPORT</a><br>
+<br><a name="SEC4" href="#TOC1">UNICODE CHARACTER PROPERTY SUPPORT</a><br>
 <P>
 UTF-8 support allows PCRE to process character values greater than 255 in the
 strings that it handles. On its own, however, it does not provide any
@@ -72,7 +83,7 @@ such as <i>Lu</i> and <i>Nd</i> are supported. Details are given in the
 <a href="pcrepattern.html"><b>pcrepattern</b></a>
 documentation.
 </P>
-<br><a name="SEC4" href="#TOC1">CODE VALUE OF NEWLINE</a><br>
+<br><a name="SEC5" href="#TOC1">CODE VALUE OF NEWLINE</a><br>
 <P>
 By default, PCRE treats character 10 (linefeed) as the newline character. This
 is the normal newline character on Unix-like systems. You can compile PCRE to
@@ -84,7 +95,7 @@ to the <b>configure</b> command. For completeness there is also a
 --enable-newline-is-lf option, which explicitly specifies linefeed as the
 newline character.
 </P>
-<br><a name="SEC5" href="#TOC1">BUILDING SHARED AND STATIC LIBRARIES</a><br>
+<br><a name="SEC6" href="#TOC1">BUILDING SHARED AND STATIC LIBRARIES</a><br>
 <P>
 The PCRE building process uses <b>libtool</b> to build both shared and static
 Unix libraries by default. You can suppress one of these by adding one of
@@ -94,7 +105,7 @@ Unix libraries by default. You can suppress one of these by adding one of
 </pre>
 to the <b>configure</b> command, as required.
 </P>
-<br><a name="SEC6" href="#TOC1">POSIX MALLOC USAGE</a><br>
+<br><a name="SEC7" href="#TOC1">POSIX MALLOC USAGE</a><br>
 <P>
 When PCRE is called through the POSIX interface (see the
 <a href="pcreposix.html"><b>pcreposix</b></a>
@@ -110,7 +121,7 @@ such as
 </pre>
 to the <b>configure</b> command.
 </P>
-<br><a name="SEC7" href="#TOC1">LIMITING PCRE RESOURCE USAGE</a><br>
+<br><a name="SEC8" href="#TOC1">LIMITING PCRE RESOURCE USAGE</a><br>
 <P>
 Internally, PCRE has a function called <b>match()</b>, which it calls repeatedly
 (possibly recursively) when matching a pattern with the <b>pcre_exec()</b>
@@ -127,7 +138,7 @@ setting such as
 to the <b>configure</b> command. This setting has no effect on the
 <b>pcre_dfa_exec()</b> matching function.
 </P>
-<br><a name="SEC8" href="#TOC1">HANDLING VERY LARGE PATTERNS</a><br>
+<br><a name="SEC9" href="#TOC1">HANDLING VERY LARGE PATTERNS</a><br>
 <P>
 Within a compiled pattern, offset values are used to point from one part to
 another (for example, from an opening parenthesis to an alternation
@@ -148,7 +159,7 @@ If you build PCRE with an increased link size, test 2 (and test 5 if you are
 using UTF-8) will fail. Part of the output of these tests is a representation
 of the compiled pattern, and this changes with the link size.
 </P>
-<br><a name="SEC9" href="#TOC1">AVOIDING EXCESSIVE STACK USAGE</a><br>
+<br><a name="SEC10" href="#TOC1">AVOIDING EXCESSIVE STACK USAGE</a><br>
 <P>
 When matching with the <b>pcre_exec()</b> function, PCRE implements backtracking
 by making recursive calls to an internal function called <b>match()</b>. In
@@ -171,7 +182,7 @@ optimized functions that perform better than the standard <b>malloc()</b> and
 way. This option affects only the <b>pcre_exec()</b> function; it is not
 relevant for the the <b>pcre_dfa_exec()</b> function.
 </P>
-<br><a name="SEC10" href="#TOC1">USING EBCDIC CODE</a><br>
+<br><a name="SEC11" href="#TOC1">USING EBCDIC CODE</a><br>
 <P>
 PCRE assumes by default that it will run in an environment where the character
 code is ASCII (or Unicode, which is a superset of ASCII). PCRE can, however, be
@@ -182,7 +193,7 @@ compiled to run in an EBCDIC environment by adding
 to the <b>configure</b> command.
 </P>
 <P>
-Last updated: 28 February 2005
+Last updated: 15 August 2005
 <br>
 Copyright &copy; 1997-2005 University of Cambridge.
 <p>