17 |
<li><a name="TOC2" href="#SEC2">SAVING A COMPILED PATTERN</a> |
<li><a name="TOC2" href="#SEC2">SAVING A COMPILED PATTERN</a> |
18 |
<li><a name="TOC3" href="#SEC3">RE-USING A PRECOMPILED PATTERN</a> |
<li><a name="TOC3" href="#SEC3">RE-USING A PRECOMPILED PATTERN</a> |
19 |
<li><a name="TOC4" href="#SEC4">COMPATIBILITY WITH DIFFERENT PCRE RELEASES</a> |
<li><a name="TOC4" href="#SEC4">COMPATIBILITY WITH DIFFERENT PCRE RELEASES</a> |
20 |
|
<li><a name="TOC5" href="#SEC5">AUTHOR</a> |
21 |
|
<li><a name="TOC6" href="#SEC6">REVISION</a> |
22 |
</ul> |
</ul> |
23 |
<br><a name="SEC1" href="#TOC1">SAVING AND RE-USING PRECOMPILED PCRE PATTERNS</a><br> |
<br><a name="SEC1" href="#TOC1">SAVING AND RE-USING PRECOMPILED PCRE PATTERNS</a><br> |
24 |
<P> |
<P> |
34 |
If you save compiled patterns to a file, you can copy them to a different host |
If you save compiled patterns to a file, you can copy them to a different host |
35 |
and run them there. This works even if the new host has the opposite endianness |
and run them there. This works even if the new host has the opposite endianness |
36 |
to the one on which the patterns were compiled. There may be a small |
to the one on which the patterns were compiled. There may be a small |
37 |
performance penalty, but it should be insignificant. |
performance penalty, but it should be insignificant. However, compiling regular |
38 |
|
expressions with one version of PCRE for use with a different version is not |
39 |
|
guaranteed to work and may cause crashes. |
40 |
</P> |
</P> |
41 |
<br><a name="SEC2" href="#TOC1">SAVING A COMPILED PATTERN</a><br> |
<br><a name="SEC2" href="#TOC1">SAVING A COMPILED PATTERN</a><br> |
42 |
<P> |
<P> |
124 |
</P> |
</P> |
125 |
<br><a name="SEC4" href="#TOC1">COMPATIBILITY WITH DIFFERENT PCRE RELEASES</a><br> |
<br><a name="SEC4" href="#TOC1">COMPATIBILITY WITH DIFFERENT PCRE RELEASES</a><br> |
126 |
<P> |
<P> |
127 |
The layout of the control block that is at the start of the data that makes up |
In general, it is safest to recompile all saved patterns when you update to a |
128 |
a compiled pattern was changed for release 5.0. If you have any saved patterns |
new PCRE release, though not all updates actually require this. Recompiling is |
129 |
that were compiled with previous releases (not a facility that was previously |
definitely needed for release 7.2. |
|
advertised), you will have to recompile them for release 5.0 and above. |
|
130 |
</P> |
</P> |
131 |
|
<br><a name="SEC5" href="#TOC1">AUTHOR</a><br> |
132 |
<P> |
<P> |
133 |
If you have any saved patterns in UTF-8 mode that use \p or \P that were |
Philip Hazel |
134 |
compiled with any release up to and including 6.4, you will have to recompile |
<br> |
135 |
them for release 6.5 and above. |
University Computing Service |
136 |
</P> |
<br> |
137 |
<P> |
Cambridge CB2 3QH, England. |
138 |
All saved patterns from earlier releases must be recompiled for release 7.0 or |
<br> |
|
higher, because there was an internal reorganization at that release. |
|
139 |
</P> |
</P> |
140 |
|
<br><a name="SEC6" href="#TOC1">REVISION</a><br> |
141 |
<P> |
<P> |
142 |
Last updated: 28 November 2006 |
Last updated: 13 June 2007 |
143 |
|
<br> |
144 |
|
Copyright © 1997-2007 University of Cambridge. |
145 |
<br> |
<br> |
|
Copyright © 1997-2006 University of Cambridge. |
|
146 |
<p> |
<p> |
147 |
Return to the <a href="index.html">PCRE index page</a>. |
Return to the <a href="index.html">PCRE index page</a>. |
148 |
</p> |
</p> |