/[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 744 by zherczeg, Sun Nov 13 16:31:38 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    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 and \u in JavaScript compatibility mode based on the
21        ECMA-262 standard.
22    
23    
24    Version 8.20 21-Oct-2011
25  ------------------------  ------------------------
26    
27  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 85  Version 8.20 10-Oct-2011
85      pattern contains any instances of (*THEN). If it does not, the old      pattern contains any instances of (*THEN). If it does not, the old
86      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
87      basis, but at the moment that is not feasible.      basis, but at the moment that is not feasible.
88    
89  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
90      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
91      after the value is now allowed for.      character after the value is now allowed for.
92    
93  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".
94      For "fr", it uses the Windows-specific input and output files.      For "fr", it uses the Windows-specific input and output files.
95    
96  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
97      subroutine, it did not work as intended. [But see next item.]      subroutine, it did not work as intended. [But see next item.]
98    
99  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
100      pattern fragments (but not containing any | characters). If A and B are      pattern fragments (but not containing any | characters). If A and B are
101      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
102      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
103      D. In other words, Perl considers parentheses that do not contain any |      D. In other words, Perl considers parentheses that do not contain any |
104      characters to be part of a surrounding alternative, whereas PCRE was      characters to be part of a surrounding alternative, whereas PCRE was
105      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
106      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
107      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
108      been different (but PCRE had them first :-).      been different (but PCRE had them first :-).
109    
110  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
111      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
112      ordinary group without any | characters when processing (*THEN). PCRE has      ordinary group without any | characters when processing (*THEN). PCRE has
113      been changed to match Perl's behaviour.      been changed to match Perl's behaviour.
114    
115  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
116      RunGrepTest script failed.      RunGrepTest script failed.
117    
118  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
119      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
120      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
121      groups that do not contain any capturing parentheses.      groups that do not contain any capturing parentheses.
122    
123  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
124      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
125      given to pcre_exec() or pcre_dfa_exec() it did work.)      given to pcre_exec() or pcre_dfa_exec() it did work.)
126    
127    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
128        fail to work when decoding hex characters in data strings in EBCDIC
129        environments.
130    
131    21. It appears that in at least one Mac OS environment, the isxdigit() function
132        is implemented as a macro that evaluates to its argument more than once,
133        contravening the C 90 Standard (I haven't checked a later standard). There
134        was an instance in pcretest which caused it to go wrong when processing
135        \x{...} escapes in subject strings. The has been rewritten to avoid using
136        things like p++ in the argument of isxdigit().
137    
138    
139  Version 8.13 16-Aug-2011  Version 8.13 16-Aug-2011

Legend:
Removed from v.729  
changed lines
  Added in v.744

  ViewVC Help
Powered by ViewVC 1.1.5