1 |
ChangeLog for PCRE |
ChangeLog for PCRE |
2 |
------------------ |
------------------ |
3 |
|
|
4 |
Version 8.20 10-Oct-2011 |
Version 8.21 |
5 |
|
------------ |
6 |
|
|
7 |
|
1. Updating the JIT compiler. |
8 |
|
|
9 |
|
2. JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases |
10 |
|
are added as well. |
11 |
|
|
12 |
|
3. Fix cache-flush issue on PowerPC (It is still an experimental JIT port). |
13 |
|
PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before |
14 |
|
calling _pcre_jit_exec. Some extra comments are added. |
15 |
|
|
16 |
|
4. Mark settings inside atomic groups that do not contain any capturing |
17 |
|
parentheses, for example, (?>a(*:m)), were not being passed out. This bug |
18 |
|
was introduced by change 18 for 8.20. |
19 |
|
|
20 |
|
5. Supporting of \x, \U and \u in JavaScript compatibility mode based on the |
21 |
|
ECMA-262 standard. |
22 |
|
|
23 |
|
6. Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were |
24 |
|
erroneously being rejected as "not fixed length" if PCRE_CASELESS was set. |
25 |
|
This bug was probably introduced by change 9 of 8.13. |
26 |
|
|
27 |
|
7. While fixing 6 above, I noticed that a number of other items were being |
28 |
|
incorrectly rejected as "not fixed length". This arose partly because newer |
29 |
|
opcodes had not been added to the fixed-length checking code. I have (a) |
30 |
|
corrected the bug and added tests for these items, and (b) arranged for an |
31 |
|
error to occur if an unknown opcode is encountered while checking for fixed |
32 |
|
length instead of just assuming "not fixed length". The items that were |
33 |
|
rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP), |
34 |
|
(*THEN), \h, \H, \v, \V, and single character negative classes with fixed |
35 |
|
repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS. |
36 |
|
|
37 |
|
8. A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was |
38 |
|
being incorrectly compiled and would have given unpredicatble results. |
39 |
|
|
40 |
|
9. A possessively repeated subpattern with minimum repeat count greater than |
41 |
|
one behaved incorrectly. For example, (A){2,}+ behaved as if it was |
42 |
|
(A)(A)++ which meant that, after a subsequent mismatch, backtracking into |
43 |
|
the first (A) could occur when it should not. |
44 |
|
|
45 |
|
|
46 |
|
Version 8.20 21-Oct-2011 |
47 |
------------------------ |
------------------------ |
48 |
|
|
49 |
1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had |
1. Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had |
110 |
|
|
111 |
12. In some environments, the output of pcretest -C is CRLF terminated. This |
12. In some environments, the output of pcretest -C is CRLF terminated. This |
112 |
broke RunTest's code that checks for the link size. A single white space |
broke RunTest's code that checks for the link size. A single white space |
113 |
after the value is now allowed for. |
character after the value is now allowed for. |
114 |
|
|
115 |
13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french". |
13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french". |
116 |
For "fr", it uses the Windows-specific input and output files. |
For "fr", it uses the Windows-specific input and output files. |
146 |
suppress the check for a minimum subject length at run time. (If it was |
suppress the check for a minimum subject length at run time. (If it was |
147 |
given to pcre_exec() or pcre_dfa_exec() it did work.) |
given to pcre_exec() or pcre_dfa_exec() it did work.) |
148 |
|
|
149 |
|
20. Fixed an ASCII-dependent infelicity in pcretest that would have made it |
150 |
|
fail to work when decoding hex characters in data strings in EBCDIC |
151 |
|
environments. |
152 |
|
|
153 |
|
21. It appears that in at least one Mac OS environment, the isxdigit() function |
154 |
|
is implemented as a macro that evaluates to its argument more than once, |
155 |
|
contravening the C 90 Standard (I haven't checked a later standard). There |
156 |
|
was an instance in pcretest which caused it to go wrong when processing |
157 |
|
\x{...} escapes in subject strings. The has been rewritten to avoid using |
158 |
|
things like p++ in the argument of isxdigit(). |
159 |
|
|
160 |
|
|
161 |
Version 8.13 16-Aug-2011 |
Version 8.13 16-Aug-2011 |
162 |
------------------------ |
------------------------ |