118 |
property table); only the basic two-letter properties such as Lu are |
property table); only the basic two-letter properties such as Lu are |
119 |
supported. |
supported. |
120 |
|
|
121 |
. You can build PCRE to recognize either CR or LF or the sequence CRLF as |
. You can build PCRE to recognize either CR or LF or the sequence CRLF or any |
122 |
indicating the end of a line. Whatever you specify at build time is the |
of the Unicode newline sequences as indicating the end of a line. Whatever |
123 |
default; the caller of PCRE can change the selection at run time. The default |
you specify at build time is the default; the caller of PCRE can change the |
124 |
newline indicator is a single LF character (the Unix standard). You can |
selection at run time. The default newline indicator is a single LF character |
125 |
specify the default newline indicator by adding --newline-is-cr or |
(the Unix standard). You can specify the default newline indicator by adding |
126 |
--newline-is-lf or --newline-is-crlf to the "configure" command, |
--newline-is-cr or --newline-is-lf or --newline-is-crlf or --newline-is-any |
127 |
respectively. |
to the "configure" command, respectively. |
128 |
|
|
129 |
. When called via the POSIX interface, PCRE uses malloc() to get additional |
. When called via the POSIX interface, PCRE uses malloc() to get additional |
130 |
storage for processing capturing parentheses if there are more than 10 of |
storage for processing capturing parentheses if there are more than 10 of |
283 |
Using HP's ANSI C++ compiler (aCC) |
Using HP's ANSI C++ compiler (aCC) |
284 |
---------------------------------- |
---------------------------------- |
285 |
|
|
286 |
Unless C++ support is disabled by specifiying the "--disable-cpp" option of the |
Unless C++ support is disabled by specifying the "--disable-cpp" option of the |
287 |
"configure" script, you *must* include the "-AA" option in the CXXFLAGS |
"configure" script, you *must* include the "-AA" option in the CXXFLAGS |
288 |
environment variable in order for the C++ components to compile correctly. |
environment variable in order for the C++ components to compile correctly. |
289 |
|
|
305 |
|
|
306 |
PCRE has been compiled on Windows systems and on Macintoshes, but I don't know |
PCRE has been compiled on Windows systems and on Macintoshes, but I don't know |
307 |
the details because I don't use those systems. It should be straightforward to |
the details because I don't use those systems. It should be straightforward to |
308 |
build PCRE on any system that has a Standard C compiler, because it uses only |
build PCRE on any system that has a Standard C compiler and library, because it |
309 |
Standard C functions. |
uses only Standard C functions. |
310 |
|
|
311 |
|
|
312 |
Testing PCRE |
Testing PCRE |
325 |
The RunTest script runs the pcretest test program (which is documented in its |
The RunTest script runs the pcretest test program (which is documented in its |
326 |
own man page) on each of the testinput files (in the testdata directory) in |
own man page) on each of the testinput files (in the testdata directory) in |
327 |
turn, and compares the output with the contents of the corresponding testoutput |
turn, and compares the output with the contents of the corresponding testoutput |
328 |
file. A file called testtry is used to hold the main output from pcretest |
files. A file called testtry is used to hold the main output from pcretest |
329 |
(testsavedregex is also used as a working file). To run pcretest on just one of |
(testsavedregex is also used as a working file). To run pcretest on just one of |
330 |
the test files, give its number as an argument to RunTest, for example: |
the test files, give its number as an argument to RunTest, for example: |
331 |
|
|
332 |
RunTest 2 |
RunTest 2 |
333 |
|
|
334 |
The first file can also be fed directly into the perltest script to check that |
The first test file can also be fed directly into the perltest script to check |
335 |
Perl gives the same results. The only difference you should see is in the first |
that Perl gives the same results. The only difference you should see is in the |
336 |
few lines, where the Perl version is given instead of the PCRE version. |
first few lines, where the Perl version is given instead of the PCRE version. |
337 |
|
|
338 |
The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(), |
The second set of tests check pcre_fullinfo(), pcre_info(), pcre_study(), |
339 |
pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error |
pcre_copy_substring(), pcre_get_substring(), pcre_get_substring_list(), error |
442 |
pcre_globals.c ) and some internal functions that they use |
pcre_globals.c ) and some internal functions that they use |
443 |
pcre_info.c ) |
pcre_info.c ) |
444 |
pcre_maketables.c ) |
pcre_maketables.c ) |
445 |
|
pcre_newline.c ) |
446 |
pcre_ord2utf8.c ) |
pcre_ord2utf8.c ) |
447 |
pcre_refcount.c ) |
pcre_refcount.c ) |
448 |
pcre_study.c ) |
pcre_study.c ) |
526 |
Philip Hazel |
Philip Hazel |
527 |
Email local part: ph10 |
Email local part: ph10 |
528 |
Email domain: cam.ac.uk |
Email domain: cam.ac.uk |
529 |
June 2006 |
November 2006 |