diff options
author | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2011-08-23 16:45:55 +0000 |
---|---|---|
committer | ph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15> | 2011-08-23 16:45:55 +0000 |
commit | dab7f58df475a277ee87a3121f42342d05617775 (patch) | |
tree | 15728872a955e8c47b447ab4986f915dac3735a2 /HACKING | |
parent | 1d802a43983c10a4874fc5f014dec121722ad5f8 (diff) | |
download | pcre-dab7f58df475a277ee87a3121f42342d05617775.tar.gz |
Update non-manpage documentation for JIT.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@672 2f5784b3-3f2a-0410-8824-cb99058d5e15
Diffstat (limited to 'HACKING')
-rw-r--r-- | HACKING | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -89,7 +89,10 @@ The "traditional", and original, matching function is called pcre_exec(), and it implements an NFA algorithm, similar to the original Henry Spencer algorithm and the way that Perl works. This is not surprising, since it is intended to be as compatible with Perl as possible. This is the function most users of PCRE -will use most of the time. +will use most of the time. From release 8.20, if PCRE is compiled with +just-in-time (JIT) support, and studying a compiled pattern with JIT is +successful, the JIT code is run instead of the normal pcre_exec() code, but the +result is the same. Supplementary matching function @@ -450,4 +453,4 @@ next item. Philip Hazel -July 2011 +August 2011 |