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

Diff of /code/trunk/ChangeLog

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

revision 729 by ph10, Mon Oct 10 16:02:20 2011 UTC revision 742 by zherczeg, Sun Nov 6 08:05:33 2011 UTC
# Line 1  Line 1 
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    
17    Version 8.20 21-Oct-2011
18  ------------------------  ------------------------
19    
20  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 10-Oct-2011 Line 78  Version 8.20 10-Oct-2011
78      pattern contains any instances of (*THEN). If it does not, the old      pattern contains any instances of (*THEN). If it does not, the old
79      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
80      basis, but at the moment that is not feasible.      basis, but at the moment that is not feasible.
81    
82  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
83      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
84      after the value is now allowed for.      character after the value is now allowed for.
85    
86  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".
87      For "fr", it uses the Windows-specific input and output files.      For "fr", it uses the Windows-specific input and output files.
88    
89  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
90      subroutine, it did not work as intended. [But see next item.]      subroutine, it did not work as intended. [But see next item.]
91    
92  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
93      pattern fragments (but not containing any | characters). If A and B are      pattern fragments (but not containing any | characters). If A and B are
94      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
95      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
96      D. In other words, Perl considers parentheses that do not contain any |      D. In other words, Perl considers parentheses that do not contain any |
97      characters to be part of a surrounding alternative, whereas PCRE was      characters to be part of a surrounding alternative, whereas PCRE was
98      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
99      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
100      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
101      been different (but PCRE had them first :-).      been different (but PCRE had them first :-).
102    
103  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
104      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
105      ordinary group without any | characters when processing (*THEN). PCRE has      ordinary group without any | characters when processing (*THEN). PCRE has
106      been changed to match Perl's behaviour.      been changed to match Perl's behaviour.
107    
108  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
109      RunGrepTest script failed.      RunGrepTest script failed.
110    
111  18. Change 22 for version 13 caused atomic groups to use more stack. This is  18. Change 22 for version 13 caused atomic groups to use more stack. This is
112      inevitable for groups that contain captures, but it can lead to a lot of      inevitable for groups that contain captures, but it can lead to a lot of
113      stack use in large patterns. The old behaviour has been restored for atomic      stack use in large patterns. The old behaviour has been restored for atomic
114      groups that do not contain any capturing parentheses.      groups that do not contain any capturing parentheses.
115    
116  19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not  19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
117      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
118      given to pcre_exec() or pcre_dfa_exec() it did work.)      given to pcre_exec() or pcre_dfa_exec() it did work.)
119    
120    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
121        fail to work when decoding hex characters in data strings in EBCDIC
122        environments.
123    
124    21. It appears that in at least one Mac OS environment, the isxdigit() function
125        is implemented as a macro that evaluates to its argument more than once,
126        contravening the C 90 Standard (I haven't checked a later standard). There
127        was an instance in pcretest which caused it to go wrong when processing
128        \x{...} escapes in subject strings. The has been rewritten to avoid using
129        things like p++ in the argument of isxdigit().
130    
131    
132  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011
Legend:
Removed from v.729  
changed lines
  Added in v.742
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12