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

Diff of /code/trunk/ChangeLog

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

revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC revision 932 by ph10, Fri Feb 24 18:54:43 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.13 02-Aug-2011  Version 8.31
5    -----------------------------
6    
7    1.  Fixing a wrong JIT test case and some compiler warnings.
8    
9    2.  Removed a bashism from the RunTest script.
10    
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
14    
15    4.  Partial matching support is added to the JIT compiler.
16    
17    5.  Fixed several bugs concerned with partial matching of items that consist
18        of more than one character:
19    
20        (a) /^(..)\1/ did not partially match "aba" because checking references was
21            done on an "all or nothing" basis. This also applied to repeated
22            references.
23    
24        (b) \R did not give a hard partial match if \r was found at the end of the
25            subject.
26    
27        (c) \X did not give a hard partial match after matching one or more
28            characters at the end of the subject.
29    
30        (d) When newline was set to CRLF, a pattern such as /a$/ did not recognize
31            a partial match for the string "\r".
32    
33        (e) When newline was set to CRLF, the metacharacter "." did not recognize
34            a partial match for a CR character at the end of the subject string.
35    
36    6.  If JIT is requested using /S++ or -s++ (instead of just /S+ or -s+) when
37        running pcretest, the text "(JIT)" added to the output whenever JIT is
38        actually used to run the match.
39    
40    7.  Individual JIT compile options can be set in pcretest by following -s+[+]
41        or /S+[+] with a digit between 1 and 7.
42    
43    8.  OP_NOT now supports any UTF character not just single-byte ones.
44    
45    9.  (*MARK) control verb is now supported by the JIT compiler.
46    
47    10. The command "./RunTest list" lists the available tests without actually
48        running any of them. (Because I keep forgetting what they all are.)
49    
50    11. Add PCRE_INFO_MAXLOOKBEHIND.
51    
52    
53    Version 8.30 04-February-2012
54    -----------------------------
55    
56    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
57        name is defined in ctype.h.
58    
59    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
60        only in quite long subpatterns.
61    
62    3.  Removed the function pcre_info(), which has been obsolete and deprecated
63        since it was replaced by pcre_fullinfo() in February 2000.
64    
65    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
66        match a (*MARK), and the match failed at the start of the subject, a
67        reference to memory before the start of the subject could occur. This bug
68        was introduced by fix 17 of release 8.21.
69    
70    5.  A reference to an unset group with zero minimum repetition was giving
71        totally wrong answers (in non-JavaScript-compatibility mode). For example,
72        /(another)?(\1?)test/ matched against "hello world test". This bug was
73        introduced in release 8.13.
74    
75    6.  Add support for 16-bit character strings (a large amount of work involving
76        many changes and refactorings).
77    
78    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
79        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
80        from a file.
81    
82    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
83        rounding is not applied in this particular case).
84    
85    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
86        if they appear, or are escaped, in patterns.
87    
88    10. Get rid of a number of -Wunused-but-set-variable warnings.
89    
90    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
91        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
92        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
93        also returns the mark "x". This bug applied to capturing parentheses,
94        non-capturing parentheses, and atomic parentheses. It also applied to some
95        assertions.
96    
97    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
98        information out of configure.ac instead of relying on pcre.h.generic, which
99        is not stored in the repository.
100    
101    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
102        -lreadline.
103    
104    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
105    
106    15. Applied Graycode's patch to put the top-level frame on the stack rather
107        than the heap when not using the stack for recursion. This gives a
108        performance improvement in many cases when recursion is not deep.
109    
110    16. Experimental code added to "pcretest -C" to output the stack frame size.
111    
112    
113    Version 8.21 12-Dec-2011
114    ------------------------
115    
116    1.  Updating the JIT compiler.
117    
118    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
119        are added as well.
120    
121    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
122        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
123        calling _pcre_jit_exec. Some extra comments are added.
124    
125    4.  (*MARK) settings inside atomic groups that do not contain any capturing
126        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
127        was introduced by change 18 for 8.20.
128    
129    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
130        ECMA-262 standard.
131    
132    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
133        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
134        This bug was probably introduced by change 9 of 8.13.
135    
136    7.  While fixing 6 above, I noticed that a number of other items were being
137        incorrectly rejected as "not fixed length". This arose partly because newer
138        opcodes had not been added to the fixed-length checking code. I have (a)
139        corrected the bug and added tests for these items, and (b) arranged for an
140        error to occur if an unknown opcode is encountered while checking for fixed
141        length instead of just assuming "not fixed length". The items that were
142        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
143        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
144        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
145    
146    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
147        being incorrectly compiled and would have given unpredicatble results.
148    
149    9.  A possessively repeated subpattern with minimum repeat count greater than
150        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
151        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
152        the first (A) could occur when it should not.
153    
154    10. Add a cast and remove a redundant test from the code.
155    
156    11. JIT should use pcre_malloc/pcre_free for allocation.
157    
158    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
159        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
160        is anything other than /usr, -L is still shown).
161    
162    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
163    
164    14. Perl does not support \N without a following name in a [] class; PCRE now
165        also gives an error.
166    
167    15. If a forward reference was repeated with an upper limit of around 2000,
168        it caused the error "internal error: overran compiling workspace". The
169        maximum number of forward references (including repeats) was limited by the
170        internal workspace, and dependent on the LINK_SIZE. The code has been
171        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
172        the default depends on LINK_SIZE. There is a new upper limit (for safety)
173        of around 200,000 forward references. While doing this, I also speeded up
174        the filling in of repeated forward references.
175    
176    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
177        incorrectly expecting the subject to contain another "a" after the start.
178    
179    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
180        in the match, the SKIP should be ignored. This was not happening; instead
181        the SKIP was being treated as NOMATCH. For patterns such as
182        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
183        tested.
184    
185    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
186        now much more compatible with Perl, in particular in cases where the result
187        is a non-match for a non-anchored pattern. For example, if
188        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
189        "m", where previously it did not return a name. A side effect of this
190        change is that for partial matches, the last encountered mark name is
191        returned, as for non matches. A number of tests that were previously not
192        Perl-compatible have been moved into the Perl-compatible test files. The
193        refactoring has had the pleasing side effect of removing one argument from
194        the match() function, thus reducing its stack requirements.
195    
196    19. If the /S+ option was used in pcretest to study a pattern using JIT,
197        subsequent uses of /S (without +) incorrectly behaved like /S+.
198    
199    21. Retrieve executable code size support for the JIT compiler and fixing
200        some warnings.
201    
202    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
203        not work when the shorter character appeared right at the end of the
204        subject string.
205    
206    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
207        systems.
208    
209    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
210        output it when the /M option is used in pcretest.
211    
212    25. The CheckMan script was not being included in the distribution. Also, added
213        an explicit "perl" to run Perl scripts from the PrepareRelease script
214        because this is reportedly needed in Windows.
215    
216    26. If study data was being save in a file and studying had not found a set of
217        "starts with" bytes for the pattern, the data written to the file (though
218        never used) was taken from uninitialized memory and so caused valgrind to
219        complain.
220    
221    27. Updated RunTest.bat as provided by Sheri Pierce.
222    
223    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
224    
225    29. Computation of memory usage for the table of capturing group names was
226        giving an unnecessarily large value.
227    
228    
229    Version 8.20 21-Oct-2011
230    ------------------------
231    
232    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
233        a POSIX class. After further experiments with Perl, which convinced me that
234        Perl has bugs and confusions, a closing square bracket is no longer allowed
235        in a POSIX name. This bug also affected patterns with classes that started
236        with full stops.
237    
238    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
239        captured substring, but while checking the failing first alternative,
240        substring 1 is temporarily captured. If the output vector supplied to
241        pcre_exec() was not big enough for this capture, the yield of the function
242        was still zero ("insufficient space for captured substrings"). This cannot
243        be totally fixed without adding another stack variable, which seems a lot
244        of expense for a edge case. However, I have improved the situation in cases
245        such as /(a)(b)x|abc/ matched against "abc", where the return code
246        indicates that fewer than the maximum number of slots in the ovector have
247        been set.
248    
249    3.  Related to (2) above: when there are more back references in a pattern than
250        slots in the output vector, pcre_exec() uses temporary memory during
251        matching, and copies in the captures as far as possible afterwards. It was
252        using the entire output vector, but this conflicts with the specification
253        that only 2/3 is used for passing back captured substrings. Now it uses
254        only the first 2/3, for compatibility. This is, of course, another edge
255        case.
256    
257    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
258        main code base, and can be used by building with --enable-jit. When this is
259        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
260        runtime --no-jit option is given.
261    
262    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
263        ovector, the return from the function was zero, implying that there were
264        other matches that did not fit. The correct "exactly full" value is now
265        returned.
266    
267    6.  If a subpattern that was called recursively or as a subroutine contained
268        (*PRUNE) or any other control that caused it to give a non-standard return,
269        invalid errors such as "Error -26 (nested recursion at the same subject
270        position)" or even infinite loops could occur.
271    
272    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
273        computing the minimum length on reaching *ACCEPT, and so ended up with the
274        wrong value of 1 rather than 0. Further investigation indicates that
275        computing a minimum subject length in the presence of *ACCEPT is difficult
276        (think back references, subroutine calls), and so I have changed the code
277        so that no minimum is registered for a pattern that contains *ACCEPT.
278    
279    8.  If (*THEN) was present in the first (true) branch of a conditional group,
280        it was not handled as intended. [But see 16 below.]
281    
282    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
283        Sheri Pierce.
284    
285    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
286        the first byte in a match must be "a".
287    
288    11. Change 17 for 8.13 increased the recursion depth for patterns like
289        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
290        pattern contains any instances of (*THEN). If it does not, the old
291        optimizations are restored. It would be nice to do this on a per-group
292        basis, but at the moment that is not feasible.
293    
294    12. In some environments, the output of pcretest -C is CRLF terminated. This
295        broke RunTest's code that checks for the link size. A single white space
296        character after the value is now allowed for.
297    
298    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
299        For "fr", it uses the Windows-specific input and output files.
300    
301    14. If (*THEN) appeared in a group that was called recursively or as a
302        subroutine, it did not work as intended. [But see next item.]
303    
304    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
305        pattern fragments (but not containing any | characters). If A and B are
306        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
307        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
308        D. In other words, Perl considers parentheses that do not contain any |
309        characters to be part of a surrounding alternative, whereas PCRE was
310        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
311        differently. PCRE now behaves in the same way as Perl, except in the case
312        of subroutine/recursion calls such as (?1) which have in any case always
313        been different (but PCRE had them first :-).
314    
315    16. Related to 15 above: Perl does not treat the | in a conditional group as
316        creating alternatives. Such a group is treated in the same way as an
317        ordinary group without any | characters when processing (*THEN). PCRE has
318        been changed to match Perl's behaviour.
319    
320    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
321        RunGrepTest script failed.
322    
323    18. Change 22 for version 13 caused atomic groups to use more stack. This is
324        inevitable for groups that contain captures, but it can lead to a lot of
325        stack use in large patterns. The old behaviour has been restored for atomic
326        groups that do not contain any capturing parentheses.
327    
328    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
329        suppress the check for a minimum subject length at run time. (If it was
330        given to pcre_exec() or pcre_dfa_exec() it did work.)
331    
332    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
333        fail to work when decoding hex characters in data strings in EBCDIC
334        environments.
335    
336    21. It appears that in at least one Mac OS environment, the isxdigit() function
337        is implemented as a macro that evaluates to its argument more than once,
338        contravening the C 90 Standard (I haven't checked a later standard). There
339        was an instance in pcretest which caused it to go wrong when processing
340        \x{...} escapes in subject strings. The has been rewritten to avoid using
341        things like p++ in the argument of isxdigit().
342    
343    
344    Version 8.13 16-Aug-2011
345  ------------------------  ------------------------
346    
347  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 98  Version 8.13 02-Aug-2011 Line 438  Version 8.13 02-Aug-2011
438      tail recursion to cut down on stack usage. Unfortunately, now that there is      tail recursion to cut down on stack usage. Unfortunately, now that there is
439      the possibility of (*THEN) occurring in these branches, tail recursion is      the possibility of (*THEN) occurring in these branches, tail recursion is
440      no longer possible because the return has to be checked for (*THEN). These      no longer possible because the return has to be checked for (*THEN). These
441      two optimizations have therefore been removed.      two optimizations have therefore been removed. [But see 8.20/11 above.]
442    
443  18. If a pattern containing \R was studied, it was assumed that \R always  18. If a pattern containing \R was studied, it was assumed that \R always
444      matched two bytes, thus causing the minimum subject length to be      matched two bytes, thus causing the minimum subject length to be
# Line 189  Version 8.13 02-Aug-2011 Line 529  Version 8.13 02-Aug-2011
529      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,      For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
530      unescaped square brackets may also appear as part of class names. For      unescaped square brackets may also appear as part of class names. For
531      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves      example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
532      more like Perl.      more like Perl. (But see 8.20/1 above.)
533    
534  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this  38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
535      was because it thought it was \N{name}, which is not supported).      was because it thought it was \N{name}, which is not supported).
# Line 224  Version 8.13 02-Aug-2011 Line 564  Version 8.13 02-Aug-2011
564      (a) The default value of the buffer size parameter has been increased from      (a) The default value of the buffer size parameter has been increased from
565          8K to 20K. (The actual buffer used is three times this size.)          8K to 20K. (The actual buffer used is three times this size.)
566    
567      (b) The default can be changed by ./configure --with-pcregrep-bufsiz when      (b) The default can be changed by ./configure --with-pcregrep-bufsize when
568          PCRE is built.          PCRE is built.
569    
570      (c) A --buffer-size=n option has been added to pcregrep, to allow the size      (c) A --buffer-size=n option has been added to pcregrep, to allow the size
# Line 245  Version 8.13 02-Aug-2011 Line 585  Version 8.13 02-Aug-2011
585  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a  47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
586      complete match instead of a partial match. This bug was dependent on both      complete match instead of a partial match. This bug was dependent on both
587      the PCRE_UTF8 and PCRE_DOTALL options being set.      the PCRE_UTF8 and PCRE_DOTALL options being set.
588    
589  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the  48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
590      starting byte set, because \b was not being ignored.      starting byte set, because \b was not being ignored.
591    
592    
593  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011

Legend:
Removed from v.657  
changed lines
  Added in v.932

  ViewVC Help
Powered by ViewVC 1.1.5