--- code/trunk/doc/html/pcrebuild.html 2007/02/24 21:40:45 77 +++ code/trunk/doc/html/pcrebuild.html 2007/02/24 21:41:06 83 @@ -14,15 +14,16 @@

PCRE BUILD-TIME OPTIONS

@@ -41,7 +42,17 @@ --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.

-
UTF-8 SUPPORT
+
C++ SUPPORT
+

+By default, the configure 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 +

+  --disable-cpp
+
+to the configure command. +

+
UTF-8 SUPPORT

To build PCRE with support for UTF-8 character strings, add

@@ -52,7 +63,7 @@
 have to set the PCRE_UTF8 option when you call the pcre_compile()
 function.
 

-
UNICODE CHARACTER PROPERTY SUPPORT
+
UNICODE CHARACTER PROPERTY SUPPORT

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 @@ pcrepattern documentation.

-
CODE VALUE OF NEWLINE
+
CODE VALUE OF NEWLINE

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 @@ --enable-newline-is-lf option, which explicitly specifies linefeed as the newline character.

-
BUILDING SHARED AND STATIC LIBRARIES
+
BUILDING SHARED AND STATIC LIBRARIES

The PCRE building process uses libtool to build both shared and static Unix libraries by default. You can suppress one of these by adding one of @@ -94,7 +105,7 @@

to the configure command, as required.

-
POSIX MALLOC USAGE
+
POSIX MALLOC USAGE

When PCRE is called through the POSIX interface (see the pcreposix @@ -110,7 +121,7 @@ to the configure command.

-
LIMITING PCRE RESOURCE USAGE
+
LIMITING PCRE RESOURCE USAGE

Internally, PCRE has a function called match(), which it calls repeatedly (possibly recursively) when matching a pattern with the pcre_exec() @@ -127,7 +138,7 @@ to the configure command. This setting has no effect on the pcre_dfa_exec() matching function.

-
HANDLING VERY LARGE PATTERNS
+
HANDLING VERY LARGE PATTERNS

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 @@ 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.

-
AVOIDING EXCESSIVE STACK USAGE
+
AVOIDING EXCESSIVE STACK USAGE

When matching with the pcre_exec() function, PCRE implements backtracking by making recursive calls to an internal function called match(). In @@ -171,7 +182,7 @@ way. This option affects only the pcre_exec() function; it is not relevant for the the pcre_dfa_exec() function.

-
USING EBCDIC CODE
+
USING EBCDIC CODE

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 @@ to the configure command.

-Last updated: 28 February 2005 +Last updated: 15 August 2005
Copyright © 1997-2005 University of Cambridge.