summaryrefslogtreecommitdiff
path: root/doc/pcrejit.3
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2011-09-23 10:32:53 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2011-09-23 10:32:53 +0000
commitf55f04ace02c98b0c3441c99ae9d93ed1712efa5 (patch)
tree2ff4d168c8ecb57803467fcd45bb60548e7e311d /doc/pcrejit.3
parent1f7c50ca03b975a4adf278d85c6228d1a792748b (diff)
downloadpcre-f55f04ace02c98b0c3441c99ae9d93ed1712efa5.tar.gz
Documentation clarifications.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@707 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'doc/pcrejit.3')
-rw-r--r--doc/pcrejit.321
1 files changed, 15 insertions, 6 deletions
diff --git a/doc/pcrejit.3 b/doc/pcrejit.3
index 30d99c9..4620b6e 100644
--- a/doc/pcrejit.3
+++ b/doc/pcrejit.3
@@ -78,6 +78,9 @@ can find out if JIT execution is available after studying a pattern by calling
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 @@ execution.
.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 @@ Cambridge CB2 3QH, England.
.rs
.sp
.nf
-Last updated: 06 September 2011
+Last updated: 23 September 2011
Copyright (c) 1997-2011 University of Cambridge.
.fi