/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 720 by ph10, Fri Oct 7 15:18:21 2011 UTC revision 749 by ph10, Fri Nov 18 10:36:45 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.20 23-Sep-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    
41    Version 8.20 21-Oct-2011
42  ------------------------  ------------------------
43    
44  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
# Line 65  Version 8.20 23-Sep-2011 Line 102  Version 8.20 23-Sep-2011
102      pattern contains any instances of (*THEN). If it does not, the old      pattern contains any instances of (*THEN). If it does not, the old
103      optimizations are restored. It would be nice to do this on a per-group      optimizations are restored. It would be nice to do this on a per-group
104      basis, but at the moment that is not feasible.      basis, but at the moment that is not feasible.
105    
106  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
107      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
108      after the value is now allowed for.      character after the value is now allowed for.
109    
110  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".
111      For "fr", it uses the Windows-specific input and output files.      For "fr", it uses the Windows-specific input and output files.
112    
113  14. If (*THEN) appeared in a group that was called recursively or as a  14. If (*THEN) appeared in a group that was called recursively or as a
114      subroutine, it did not work as intended. [But see next item.]      subroutine, it did not work as intended. [But see next item.]
115    
116  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex  15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
117      pattern fragments (but not containing any | characters). If A and B are      pattern fragments (but not containing any | characters). If A and B are
118      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE      matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
119      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to      was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
120      D. In other words, Perl considers parentheses that do not contain any |      D. In other words, Perl considers parentheses that do not contain any |
121      characters to be part of a surrounding alternative, whereas PCRE was      characters to be part of a surrounding alternative, whereas PCRE was
122      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles      treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
123      differently. PCRE now behaves in the same way as Perl, except in the case      differently. PCRE now behaves in the same way as Perl, except in the case
124      of subroutine/recursion calls such as (?1) which have in any case always      of subroutine/recursion calls such as (?1) which have in any case always
125      been different (but PCRE had them first :-).      been different (but PCRE had them first :-).
126    
127  16. Related to 15 above: Perl does not treat the | in a conditional group as  16. Related to 15 above: Perl does not treat the | in a conditional group as
128      creating alternatives. Such a group is treated in the same way as an      creating alternatives. Such a group is treated in the same way as an
129      ordinary group without any | characters when processing (*THEN). PCRE has      ordinary group without any | characters when processing (*THEN). PCRE has
130      been changed to match Perl's behaviour.      been changed to match Perl's behaviour.
131    
132  17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the  17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
133      RunGrepTest script failed.      RunGrepTest script failed.
134    
135    18. Change 22 for version 13 caused atomic groups to use more stack. This is
136        inevitable for groups that contain captures, but it can lead to a lot of
137        stack use in large patterns. The old behaviour has been restored for atomic
138        groups that do not contain any capturing parentheses.
139    
140    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
141        suppress the check for a minimum subject length at run time. (If it was
142        given to pcre_exec() or pcre_dfa_exec() it did work.)
143    
144    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
145        fail to work when decoding hex characters in data strings in EBCDIC
146        environments.
147    
148    21. It appears that in at least one Mac OS environment, the isxdigit() function
149        is implemented as a macro that evaluates to its argument more than once,
150        contravening the C 90 Standard (I haven't checked a later standard). There
151        was an instance in pcretest which caused it to go wrong when processing
152        \x{...} escapes in subject strings. The has been rewritten to avoid using
153        things like p++ in the argument of isxdigit().
154    
155    
156  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011

Legend:
Removed from v.720  
changed lines
  Added in v.749

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12