Revision: 707
http://vcs.pcre.org/viewvc?view=rev&revision=707
Author: ph10
Date: 2011-09-23 11:32:53 +0100 (Fri, 23 Sep 2011)
Log Message:
-----------
Documentation clarifications.
Modified Paths:
--------------
code/trunk/doc/pcreapi.3
code/trunk/doc/pcrejit.3
Modified: code/trunk/doc/pcreapi.3
===================================================================
--- code/trunk/doc/pcreapi.3 2011-09-23 10:11:35 UTC (rev 706)
+++ code/trunk/doc/pcreapi.3 2011-09-23 10:32:53 UTC (rev 707)
@@ -1331,9 +1331,13 @@
The function \fBpcre_exec()\fP is called to match a subject string against a
compiled pattern, which is passed in the \fIcode\fP argument. If the
pattern was studied, the result of the study should be passed in the
-\fIextra\fP argument. This function is the main matching facility of the
-library, and it operates in a Perl-like manner. For specialist use there is
-also an alternative matching function, which is described
+\fIextra\fP argument. You can call \fBpcre_exec()\fP with the same \fIcode\fP
+and \fIextra\fP arguments as many times as you like, in order to match
+different subject strings with the same pattern.
+.P
+This function is the main matching facility of the library, and it operates in
+a Perl-like manner. For specialist use there is also an alternative matching
+function, which is described
.\" HTML <a href="#dfamatch">
.\" </a>
below
@@ -2526,6 +2530,6 @@
.rs
.sp
.nf
-Last updated: 06 September 2011
+Last updated: 23 September 2011
Copyright (c) 1997-2011 University of Cambridge.
.fi
Modified: code/trunk/doc/pcrejit.3
===================================================================
--- code/trunk/doc/pcrejit.3 2011-09-23 10:11:35 UTC (rev 706)
+++ code/trunk/doc/pcrejit.3 2011-09-23 10:32:53 UTC (rev 707)
@@ -78,6 +78,9 @@
JIT compilation was successful. A result of 0 means that JIT support is not
available, or the pattern was not studied with PCRE_STUDY_JIT_COMPILE, or the
JIT compiler was not able to handle the pattern.
+.P
+Once a pattern has been studied, with or without JIT, it can be used as many
+times as you like for matching different subject strings.
.
.
.SH "UNSUPPORTED OPTIONS AND PATTERN ITEMS"
@@ -131,11 +134,17 @@
.rs
.sp
The code that is generated by the JIT compiler is architecture-specific, and is
-also position dependent. For those reasons it cannot be saved and restored like
-the bytecode and other data of a compiled pattern. You should be able run
-\fBpcre_study()\fP on a saved and restored pattern, and thereby recreate the
-JIT data, but because JIT compilation uses significant resources, it is
-probably not worth doing this.
+also position dependent. For those reasons it cannot be saved (in a file or
+database) and restored later like the bytecode and other data of a compiled
+pattern. Saving and restoring compiled patterns is not something many people
+do. More detail about this facility is given in the
+.\" HREF
+\fBpcreprecompile\fP
+.\"
+documentation. It should be possible to run \fBpcre_study()\fP on a saved and
+restored pattern, and thereby recreate the JIT data, but because JIT
+compilation uses significant resources, it is probably not worth doing this;
+you might as well recompile the original pattern.
.
.
.\" HTML <a name="stackcontrol"></a>
@@ -256,6 +265,6 @@
.rs
.sp
.nf
-Last updated: 06 September 2011
+Last updated: 23 September 2011
Copyright (c) 1997-2011 University of Cambridge.
.fi
