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

Diff of /code/trunk/ChangeLog

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

revision 505 by ph10, Tue Mar 9 16:50:47 2010 UTC revision 931 by ph10, Fri Feb 24 13:21:02 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  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    
51    Version 8.30 04-February-2012
52    -----------------------------
53    
54    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
55        name is defined in ctype.h.
56    
57    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
58        only in quite long subpatterns.
59    
60    3.  Removed the function pcre_info(), which has been obsolete and deprecated
61        since it was replaced by pcre_fullinfo() in February 2000.
62    
63    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
64        match a (*MARK), and the match failed at the start of the subject, a
65        reference to memory before the start of the subject could occur. This bug
66        was introduced by fix 17 of release 8.21.
67    
68    5.  A reference to an unset group with zero minimum repetition was giving
69        totally wrong answers (in non-JavaScript-compatibility mode). For example,
70        /(another)?(\1?)test/ matched against "hello world test". This bug was
71        introduced in release 8.13.
72    
73    6.  Add support for 16-bit character strings (a large amount of work involving
74        many changes and refactorings).
75    
76    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
77        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
78        from a file.
79    
80    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
81        rounding is not applied in this particular case).
82    
83    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
84        if they appear, or are escaped, in patterns.
85    
86    10. Get rid of a number of -Wunused-but-set-variable warnings.
87    
88    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
89        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
90        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
91        also returns the mark "x". This bug applied to capturing parentheses,
92        non-capturing parentheses, and atomic parentheses. It also applied to some
93        assertions.
94    
95    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
96        information out of configure.ac instead of relying on pcre.h.generic, which
97        is not stored in the repository.
98    
99    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
100        -lreadline.
101    
102    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
103    
104    15. Applied Graycode's patch to put the top-level frame on the stack rather
105        than the heap when not using the stack for recursion. This gives a
106        performance improvement in many cases when recursion is not deep.
107    
108    16. Experimental code added to "pcretest -C" to output the stack frame size.
109    
110    
111    Version 8.21 12-Dec-2011
112    ------------------------
113    
114    1.  Updating the JIT compiler.
115    
116    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
117        are added as well.
118    
119    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
120        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
121        calling _pcre_jit_exec. Some extra comments are added.
122    
123    4.  (*MARK) settings inside atomic groups that do not contain any capturing
124        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
125        was introduced by change 18 for 8.20.
126    
127    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
128        ECMA-262 standard.
129    
130    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
131        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
132        This bug was probably introduced by change 9 of 8.13.
133    
134    7.  While fixing 6 above, I noticed that a number of other items were being
135        incorrectly rejected as "not fixed length". This arose partly because newer
136        opcodes had not been added to the fixed-length checking code. I have (a)
137        corrected the bug and added tests for these items, and (b) arranged for an
138        error to occur if an unknown opcode is encountered while checking for fixed
139        length instead of just assuming "not fixed length". The items that were
140        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
141        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
142        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
143    
144    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
145        being incorrectly compiled and would have given unpredicatble results.
146    
147    9.  A possessively repeated subpattern with minimum repeat count greater than
148        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
149        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
150        the first (A) could occur when it should not.
151    
152    10. Add a cast and remove a redundant test from the code.
153    
154    11. JIT should use pcre_malloc/pcre_free for allocation.
155    
156    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
157        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
158        is anything other than /usr, -L is still shown).
159    
160    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
161    
162    14. Perl does not support \N without a following name in a [] class; PCRE now
163        also gives an error.
164    
165    15. If a forward reference was repeated with an upper limit of around 2000,
166        it caused the error "internal error: overran compiling workspace". The
167        maximum number of forward references (including repeats) was limited by the
168        internal workspace, and dependent on the LINK_SIZE. The code has been
169        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
170        the default depends on LINK_SIZE. There is a new upper limit (for safety)
171        of around 200,000 forward references. While doing this, I also speeded up
172        the filling in of repeated forward references.
173    
174    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
175        incorrectly expecting the subject to contain another "a" after the start.
176    
177    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
178        in the match, the SKIP should be ignored. This was not happening; instead
179        the SKIP was being treated as NOMATCH. For patterns such as
180        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
181        tested.
182    
183    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
184        now much more compatible with Perl, in particular in cases where the result
185        is a non-match for a non-anchored pattern. For example, if
186        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
187        "m", where previously it did not return a name. A side effect of this
188        change is that for partial matches, the last encountered mark name is
189        returned, as for non matches. A number of tests that were previously not
190        Perl-compatible have been moved into the Perl-compatible test files. The
191        refactoring has had the pleasing side effect of removing one argument from
192        the match() function, thus reducing its stack requirements.
193    
194    19. If the /S+ option was used in pcretest to study a pattern using JIT,
195        subsequent uses of /S (without +) incorrectly behaved like /S+.
196    
197    21. Retrieve executable code size support for the JIT compiler and fixing
198        some warnings.
199    
200    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
201        not work when the shorter character appeared right at the end of the
202        subject string.
203    
204    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
205        systems.
206    
207    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
208        output it when the /M option is used in pcretest.
209    
210    25. The CheckMan script was not being included in the distribution. Also, added
211        an explicit "perl" to run Perl scripts from the PrepareRelease script
212        because this is reportedly needed in Windows.
213    
214    26. If study data was being save in a file and studying had not found a set of
215        "starts with" bytes for the pattern, the data written to the file (though
216        never used) was taken from uninitialized memory and so caused valgrind to
217        complain.
218    
219    27. Updated RunTest.bat as provided by Sheri Pierce.
220    
221    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
222    
223    29. Computation of memory usage for the table of capturing group names was
224        giving an unnecessarily large value.
225    
226    
227    Version 8.20 21-Oct-2011
228    ------------------------
229    
230    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
231        a POSIX class. After further experiments with Perl, which convinced me that
232        Perl has bugs and confusions, a closing square bracket is no longer allowed
233        in a POSIX name. This bug also affected patterns with classes that started
234        with full stops.
235    
236    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
237        captured substring, but while checking the failing first alternative,
238        substring 1 is temporarily captured. If the output vector supplied to
239        pcre_exec() was not big enough for this capture, the yield of the function
240        was still zero ("insufficient space for captured substrings"). This cannot
241        be totally fixed without adding another stack variable, which seems a lot
242        of expense for a edge case. However, I have improved the situation in cases
243        such as /(a)(b)x|abc/ matched against "abc", where the return code
244        indicates that fewer than the maximum number of slots in the ovector have
245        been set.
246    
247    3.  Related to (2) above: when there are more back references in a pattern than
248        slots in the output vector, pcre_exec() uses temporary memory during
249        matching, and copies in the captures as far as possible afterwards. It was
250        using the entire output vector, but this conflicts with the specification
251        that only 2/3 is used for passing back captured substrings. Now it uses
252        only the first 2/3, for compatibility. This is, of course, another edge
253        case.
254    
255    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
256        main code base, and can be used by building with --enable-jit. When this is
257        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
258        runtime --no-jit option is given.
259    
260    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
261        ovector, the return from the function was zero, implying that there were
262        other matches that did not fit. The correct "exactly full" value is now
263        returned.
264    
265    6.  If a subpattern that was called recursively or as a subroutine contained
266        (*PRUNE) or any other control that caused it to give a non-standard return,
267        invalid errors such as "Error -26 (nested recursion at the same subject
268        position)" or even infinite loops could occur.
269    
270    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
271        computing the minimum length on reaching *ACCEPT, and so ended up with the
272        wrong value of 1 rather than 0. Further investigation indicates that
273        computing a minimum subject length in the presence of *ACCEPT is difficult
274        (think back references, subroutine calls), and so I have changed the code
275        so that no minimum is registered for a pattern that contains *ACCEPT.
276    
277    8.  If (*THEN) was present in the first (true) branch of a conditional group,
278        it was not handled as intended. [But see 16 below.]
279    
280    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
281        Sheri Pierce.
282    
283    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
284        the first byte in a match must be "a".
285    
286    11. Change 17 for 8.13 increased the recursion depth for patterns like
287        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
288        pattern contains any instances of (*THEN). If it does not, the old
289        optimizations are restored. It would be nice to do this on a per-group
290        basis, but at the moment that is not feasible.
291    
292    12. In some environments, the output of pcretest -C is CRLF terminated. This
293        broke RunTest's code that checks for the link size. A single white space
294        character after the value is now allowed for.
295    
296    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
297        For "fr", it uses the Windows-specific input and output files.
298    
299    14. If (*THEN) appeared in a group that was called recursively or as a
300        subroutine, it did not work as intended. [But see next item.]
301    
302    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
303        pattern fragments (but not containing any | characters). If A and B are
304        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
305        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
306        D. In other words, Perl considers parentheses that do not contain any |
307        characters to be part of a surrounding alternative, whereas PCRE was
308        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
309        differently. PCRE now behaves in the same way as Perl, except in the case
310        of subroutine/recursion calls such as (?1) which have in any case always
311        been different (but PCRE had them first :-).
312    
313    16. Related to 15 above: Perl does not treat the | in a conditional group as
314        creating alternatives. Such a group is treated in the same way as an
315        ordinary group without any | characters when processing (*THEN). PCRE has
316        been changed to match Perl's behaviour.
317    
318    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
319        RunGrepTest script failed.
320    
321    18. Change 22 for version 13 caused atomic groups to use more stack. This is
322        inevitable for groups that contain captures, but it can lead to a lot of
323        stack use in large patterns. The old behaviour has been restored for atomic
324        groups that do not contain any capturing parentheses.
325    
326    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
327        suppress the check for a minimum subject length at run time. (If it was
328        given to pcre_exec() or pcre_dfa_exec() it did work.)
329    
330    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
331        fail to work when decoding hex characters in data strings in EBCDIC
332        environments.
333    
334    21. It appears that in at least one Mac OS environment, the isxdigit() function
335        is implemented as a macro that evaluates to its argument more than once,
336        contravening the C 90 Standard (I haven't checked a later standard). There
337        was an instance in pcretest which caused it to go wrong when processing
338        \x{...} escapes in subject strings. The has been rewritten to avoid using
339        things like p++ in the argument of isxdigit().
340    
341    
342    Version 8.13 16-Aug-2011
343    ------------------------
344    
345    1.  The Unicode data tables have been updated to Unicode 6.0.0.
346    
347    2.  Two minor typos in pcre_internal.h have been fixed.
348    
349    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
350        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
351        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
352    
353    4.  There were a number of related bugs in the code for matching backrefences
354        caselessly in UTF-8 mode when codes for the characters concerned were
355        different numbers of bytes. For example, U+023A and U+2C65 are an upper
356        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
357        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
358        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
359        2-byte code at the end of the subject (it thought there wasn't enough data
360        left).
361    
362    5.  Comprehensive information about what went wrong is now returned by
363        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
364        as the output vector has at least 2 elements. The offset of the start of
365        the failing character and a reason code are placed in the vector.
366    
367    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
368        now returned is for the first byte of the failing character, instead of the
369        last byte inspected. This is an incompatible change, but I hope it is small
370        enough not to be a problem. It makes the returned offset consistent with
371        pcre_exec() and pcre_dfa_exec().
372    
373    7.  pcretest now gives a text phrase as well as the error number when
374        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
375        failure, the offset and reason code are output.
376    
377    8.  When \R was used with a maximizing quantifier it failed to skip backwards
378        over a \r\n pair if the subsequent match failed. Instead, it just skipped
379        back over a single character (\n). This seems wrong (because it treated the
380        two characters as a single entity when going forwards), conflicts with the
381        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
382        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
383        has been changed.
384    
385    9.  Some internal refactoring has changed the processing so that the handling
386        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
387        time (the PCRE_DOTALL option was changed this way some time ago: version
388        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
389        which was always a bit of a fudge. It also means that there is one less
390        argument for the match() function, which reduces its stack requirements
391        slightly. This change also fixes an incompatibility with Perl: the pattern
392        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
393    
394    10. More internal refactoring has drastically reduced the number of recursive
395        calls to match() for possessively repeated groups such as (abc)++ when
396        using pcre_exec().
397    
398    11. While implementing 10, a number of bugs in the handling of groups were
399        discovered and fixed:
400    
401        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
402        (a|)*(?1) gave a compile-time internal error.
403        ((a|)+)+  did not notice that the outer group could match an empty string.
404        (^a|^)+   was not marked as anchored.
405        (.*a|.*)+ was not marked as matching at start or after a newline.
406    
407    12. Yet more internal refactoring has removed another argument from the match()
408        function. Special calls to this function are now indicated by setting a
409        value in a variable in the "match data" data block.
410    
411    13. Be more explicit in pcre_study() instead of relying on "default" for
412        opcodes that mean there is no starting character; this means that when new
413        ones are added and accidentally left out of pcre_study(), testing should
414        pick them up.
415    
416    14. The -s option of pcretest has been documented for ages as being an old
417        synonym of -m (show memory usage). I have changed it to mean "force study
418        for every regex", that is, assume /S for every regex. This is similar to -i
419        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
420        using it. It makes it easier to run collections of tests with and without
421        study enabled, and thereby test pcre_study() more easily. All the standard
422        tests are now run with and without -s (but some patterns can be marked as
423        "never study" - see 20 below).
424    
425    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
426        restoration of the capturing data to the outer values was not happening
427        correctly.
428    
429    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
430        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
431        pattern had matched an empty string, and so incorrectly returned a no
432        match.
433    
434    17. There was optimizing code for the last branch of non-capturing parentheses,
435        and also for the obeyed branch of a conditional subexpression, which used
436        tail recursion to cut down on stack usage. Unfortunately, now that there is
437        the possibility of (*THEN) occurring in these branches, tail recursion is
438        no longer possible because the return has to be checked for (*THEN). These
439        two optimizations have therefore been removed. [But see 8.20/11 above.]
440    
441    18. If a pattern containing \R was studied, it was assumed that \R always
442        matched two bytes, thus causing the minimum subject length to be
443        incorrectly computed because \R can also match just one byte.
444    
445    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
446        was incorrectly computed.
447    
448    20. If /S is present twice on a test pattern in pcretest input, it now
449        *disables* studying, thereby overriding the use of -s on the command line
450        (see 14 above). This is necessary for one or two tests to keep the output
451        identical in both cases.
452    
453    21. When (*ACCEPT) was used in an assertion that matched an empty string and
454        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
455    
456    22. When an atomic group that contained a capturing parenthesis was
457        successfully matched, but the branch in which it appeared failed, the
458        capturing was not being forgotten if a higher numbered group was later
459        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
460        group 1 to "a", when in fact it should be unset. This applied to multi-
461        branched capturing and non-capturing groups, repeated or not, and also to
462        positive assertions (capturing in negative assertions does not happen
463        in PCRE) and also to nested atomic groups.
464    
465    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
466        subject after a captured substring, to make it easier to tell which of a
467        number of identical substrings has been captured.
468    
469    24. The way atomic groups are processed by pcre_exec() has been changed so that
470        if they are repeated, backtracking one repetition now resets captured
471        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
472        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
473        "aaa". Previously, it would have been "a". As part of this code
474        refactoring, the way recursive calls are handled has also been changed.
475    
476    25. If an assertion condition captured any substrings, they were not passed
477        back unless some other capturing happened later. For example, if
478        (?(?=(a))a) was matched against "a", no capturing was returned.
479    
480    26. When studying a pattern that contained subroutine calls or assertions,
481        the code for finding the minimum length of a possible match was handling
482        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
483        group 1 called group 2 while simultaneously a separate group 2 called group
484        1). A stack overflow occurred in this case. I have fixed this by limiting
485        the recursion depth to 10.
486    
487    27. Updated RunTest.bat in the distribution to the version supplied by Tom
488        Fortmann. This supports explicit test numbers on the command line, and has
489        argument validation and error reporting.
490    
491    28. An instance of \X with an unlimited repeat could fail if at any point the
492        first character it looked at was a mark character.
493    
494    29. Some minor code refactoring concerning Unicode properties and scripts
495        should reduce the stack requirement of match() slightly.
496    
497    30. Added the '=' option to pcretest to check the setting of unused capturing
498        slots at the end of the pattern, which are documented as being -1, but are
499        not included in the return count.
500    
501    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
502        compiled something random. Now it gives a compile-time error (as does
503        Perl).
504    
505    32. A *MARK encountered during the processing of a positive assertion is now
506        recorded and passed back (compatible with Perl).
507    
508    33. If --only-matching or --colour was set on a pcregrep call whose pattern
509        had alternative anchored branches, the search for a second match in a line
510        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
511        matched the line "0102" twice. The same bug affected patterns that started
512        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
513        twice.
514    
515    34. Previously, PCRE did not allow quantification of assertions. However, Perl
516        does, and because of capturing effects, quantifying parenthesized
517        assertions may at times be useful. Quantifiers are now allowed for
518        parenthesized assertions.
519    
520    35. A minor code tidy in pcre_compile() when checking options for \R usage.
521    
522    36. \g was being checked for fancy things in a character class, when it should
523        just be a literal "g".
524    
525    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
526        appearance of a nested POSIX class supersedes an apparent external class.
527        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
528        unescaped square brackets may also appear as part of class names. For
529        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
530        more like Perl. (But see 8.20/1 above.)
531    
532    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
533        was because it thought it was \N{name}, which is not supported).
534    
535    39. Add minix to OS list not supporting the -S option in pcretest.
536    
537    40. PCRE tries to detect cases of infinite recursion at compile time, but it
538        cannot analyze patterns in sufficient detail to catch mutual recursions
539        such as ((?1))((?2)). There is now a runtime test that gives an error if a
540        subgroup is called recursively as a subpattern for a second time at the
541        same position in the subject string. In previous releases this might have
542        been caught by the recursion limit, or it might have run out of stack.
543    
544    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
545        happen only once. PCRE was, however incorrectly giving a compile time error
546        "recursive call could loop indefinitely" because it cannot analyze the
547        pattern in sufficient detail. The compile time test no longer happens when
548        PCRE is compiling a conditional subpattern, but actual runaway loops are
549        now caught at runtime (see 40 above).
550    
551    42. It seems that Perl allows any characters other than a closing parenthesis
552        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
553        has been changed to be the same.
554    
555    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
556        as not to get warnings when autogen.sh is called. Also changed
557        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
558    
559    44. To help people who use pcregrep to scan files containing exceedingly long
560        lines, the following changes have been made:
561    
562        (a) The default value of the buffer size parameter has been increased from
563            8K to 20K. (The actual buffer used is three times this size.)
564    
565        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
566            PCRE is built.
567    
568        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
569            to be set at run time.
570    
571        (d) Numerical values in pcregrep options can be followed by K or M, for
572            example --buffer-size=50K.
573    
574        (e) If a line being scanned overflows pcregrep's buffer, an error is now
575            given and the return code is set to 2.
576    
577    45. Add a pointer to the latest mark to the callout data block.
578    
579    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
580        partial match of an empty string instead of no match. This was specific to
581        the use of ".".
582    
583    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
584        complete match instead of a partial match. This bug was dependent on both
585        the PCRE_UTF8 and PCRE_DOTALL options being set.
586    
587    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
588        starting byte set, because \b was not being ignored.
589    
590    
591    Version 8.12 15-Jan-2011
592    ------------------------
593    
594    1.  Fixed some typos in the markup of the man pages, and wrote a script that
595        checks for such things as part of the documentation building process.
596    
597    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
598        --match-limit and --recursion-limit options (added for 8.11). In
599        particular, this made one of the standard tests fail. (The integer value
600        went into the wrong half of a long int.)
601    
602    3.  If the --colour option was given to pcregrep with -v (invert match), it
603        did strange things, either producing crazy output, or crashing. It should,
604        of course, ignore a request for colour when reporting lines that do not
605        match.
606    
607    4.  Another pcregrep bug caused similar problems if --colour was specified with
608        -M (multiline) and the pattern match finished with a line ending.
609    
610    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
611        matched in multiline mode, the following line was shown as part of the
612        match. This seems wrong, so I have changed it.
613    
614    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
615        the check for further matches in the same line (so they could be coloured)
616        to overrun the end of the current line. If another match was found, it was
617        incorrectly shown (and then shown again when found in the next line).
618    
619    7.  If pcregrep was compiled under Windows, there was a reference to the
620        function pcregrep_exit() before it was defined. I am assuming this was
621        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
622        reported by a user. I've moved the definition above the reference.
623    
624    
625    Version 8.11 10-Dec-2010
626    ------------------------
627    
628    1.  (*THEN) was not working properly if there were untried alternatives prior
629        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
630        backtracked to try for "b" instead of moving to the next alternative branch
631        at the same level (in this case, to look for "c"). The Perl documentation
632        is clear that when (*THEN) is backtracked onto, it goes to the "next
633        alternative in the innermost enclosing group".
634    
635    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
636        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
637        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
638        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
639        (*THEN).
640    
641    3.  If \s appeared in a character class, it removed the VT character from
642        the class, even if it had been included by some previous item, for example
643        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
644        of \s, but is part of the POSIX "space" class.)
645    
646    4.  A partial match never returns an empty string (because you can always
647        match an empty string at the end of the subject); however the checking for
648        an empty string was starting at the "start of match" point. This has been
649        changed to the "earliest inspected character" point, because the returned
650        data for a partial match starts at this character. This means that, for
651        example, /(?<=abc)def/ gives a partial match for the subject "abc"
652        (previously it gave "no match").
653    
654    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
655        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
656        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
657        has an implication that the given string is incomplete (because a partial
658        match is preferred over a full match). For this reason, these items now
659        give a partial match in this situation. [Aside: previously, the one case
660        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
661        match rather than a full match, which was wrong by the old rules, but is
662        now correct.]
663    
664    6.  There was a bug in the handling of #-introduced comments, recognized when
665        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
666        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
667        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
668        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
669        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
670        places in pcre_compile().
671    
672    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
673        comments when looking ahead for named forward references to subpatterns,
674        the only newline sequence it recognized was NL. It now handles newlines
675        according to the set newline convention.
676    
677    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
678        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
679        cater for a lack of strerror(). These oversights have been fixed.
680    
681    9.  Added --match-limit and --recursion-limit to pcregrep.
682    
683    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
684    
685    11. When the -o option was used, pcregrep was setting a return code of 1, even
686        when matches were found, and --line-buffered was not being honoured.
687    
688    12. Added an optional parentheses number to the -o and --only-matching options
689        of pcregrep.
690    
691    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
692        can match an empty string. The code to do it in pcretest and pcredemo
693        needed fixing:
694    
695        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
696            only one byte after an empty string match just before CRLF (this case
697            just got forgotten; "any" and "anycrlf" were OK).
698    
699        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
700            mode when an empty string match preceded an ASCII character followed by
701            a non-ASCII character. (The code for advancing by one character rather
702            than one byte was nonsense.)
703    
704        (c) The pcredemo.c sample program did not have any code at all to handle
705            the cases when CRLF is a valid newline sequence.
706    
707    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
708        as a starting offset was within the subject string. There is now a new
709        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
710        negative or greater than the length of the string. In order to test this,
711        pcretest is extended to allow the setting of negative starting offsets.
712    
713    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
714        starting offset points to the beginning of a UTF-8 character was
715        unnecessarily clumsy. I tidied it up.
716    
717    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
718        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
719    
720    17. Nobody had reported that the --include_dir option, which was added in
721        release 7.7 should have been called --include-dir (hyphen, not underscore)
722        for compatibility with GNU grep. I have changed it to --include-dir, but
723        left --include_dir as an undocumented synonym, and the same for
724        --exclude-dir, though that is not available in GNU grep, at least as of
725        release 2.5.4.
726    
727    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
728        characters from a string of bytes) have been redefined so as not to use
729        loops, in order to improve performance in some environments. At the same
730        time, I abstracted some of the common code into auxiliary macros to save
731        repetition (this should not affect the compiled code).
732    
733    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
734        compile-time error is now given if \c is not followed by an ASCII
735        character, that is, a byte less than 128. (In EBCDIC mode, the code is
736        different, and any byte value is allowed.)
737    
738    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
739        START_OPTIMIZE option, which is now allowed at compile time - but just
740        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
741        to pcregrep and other applications that have no direct access to PCRE
742        options. The new /Y option in pcretest sets this option when calling
743        pcre_compile().
744    
745    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
746        back references. Groups containing recursive back references were forced to
747        be atomic by that change, but in the case of named groups, the amount of
748        memory required was incorrectly computed, leading to "Failed: internal
749        error: code overflow". This has been fixed.
750    
751    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
752        pcretest.c, to avoid build problems in some Borland environments.
753    
754    
755    Version 8.10 25-Jun-2010
756    ------------------------
757    
758    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
759        THEN.
760    
761    2.  (*ACCEPT) was not working when inside an atomic group.
762    
763    3.  Inside a character class, \B is treated as a literal by default, but
764        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
765        causes the error). The code is unchanged, but I tidied the documentation.
766    
767    4.  Inside a character class, PCRE always treated \R and \X as literals,
768        whereas Perl faults them if its -w option is set. I have changed PCRE so
769        that it faults them when PCRE_EXTRA is set.
770    
771    5.  Added support for \N, which always matches any character other than
772        newline. (It is the same as "." when PCRE_DOTALL is not set.)
773    
774    6.  When compiling pcregrep with newer versions of gcc which may have
775        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
776        declared with attribute warn_unused_result" were given. Just casting the
777        result to (void) does not stop the warnings; a more elaborate fudge is
778        needed. I've used a macro to implement this.
779    
780    7.  Minor change to pcretest.c to avoid a compiler warning.
781    
782    8.  Added four artifical Unicode properties to help with an option to make
783        \s etc use properties (see next item). The new properties are: Xan
784        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
785    
786    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
787        use Unicode properties. (*UCP) at the start of a pattern can be used to set
788        this option. Modified pcretest to add /W to test this facility. Added
789        REG_UCP to make it available via the POSIX interface.
790    
791    10. Added --line-buffered to pcregrep.
792    
793    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
794        studied, and the match started with a letter with a code point greater than
795        127 whose first byte was different to the first byte of the other case of
796        the letter, the other case of this starting letter was not recognized
797        (#976).
798    
799    12. If a pattern that was studied started with a repeated Unicode property
800        test, for example, \p{Nd}+, there was the theoretical possibility of
801        setting up an incorrect bitmap of starting bytes, but fortunately it could
802        not have actually happened in practice until change 8 above was made (it
803        added property types that matched character-matching opcodes).
804    
805    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
806        possible starting bytes for non-anchored patterns.
807    
808    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
809        \R, and also a number of cases that involve Unicode properties, both
810        explicit and implicit when PCRE_UCP is set.
811    
812    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
813        input, it could crash or give wrong results if characters with values
814        greater than 0xc0 were present in the subject string. (Detail: it assumed
815        UTF-8 input when processing these items.)
816    
817    16. Added a lot of (int) casts to avoid compiler warnings in systems where
818        size_t is 64-bit (#991).
819    
820    17. Added a check for running out of memory when PCRE is compiled with
821        --disable-stack-for-recursion (#990).
822    
823    18. If the last data line in a file for pcretest does not have a newline on
824        the end, a newline was missing in the output.
825    
826    19. The default pcre_chartables.c file recognizes only ASCII characters (values
827        less than 128) in its various bitmaps. However, there is a facility for
828        generating tables according to the current locale when PCRE is compiled. It
829        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
830        characters, are recognized by isspace() and therefore were getting set in
831        these tables, and indeed these tables seem to approximate to ISO 8859. This
832        caused a problem in UTF-8 mode when pcre_study() was used to create a list
833        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
834        which of course cannot start UTF-8 characters. I have changed the code so
835        that only real ASCII characters (less than 128) and the correct starting
836        bytes for UTF-8 encodings are set for characters greater than 127 when in
837        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
838        altogether.)
839    
840    20. Added the /T option to pcretest so as to be able to run tests with non-
841        standard character tables, thus making it possible to include the tests
842        used for 19 above in the standard set of tests.
843    
844    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
845        reference to a subpattern the other side of a comment that contains an
846        opening parenthesis caused either an internal compiling error, or a
847        reference to the wrong subpattern.
848    
849    
850    Version 8.02 19-Mar-2010
851  ------------------------  ------------------------
852    
853  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
854    
855  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
856      configured.      configured.
857    
858  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
859      original author of that file, following a query about its status.      original author of that file, following a query about its status.
860    
861  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
862      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
863    
864  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
865      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
866      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
867      referenced subpattern not found".      referenced subpattern not found".
868    
869  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
870      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
871      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
872      relevant global functions.      relevant global functions.
873    
874  7.  There were two entries missing in the vectors called coptable and poptable  7.  There were two entries missing in the vectors called coptable and poptable
875      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
876      I've fixed the data, and added a kludgy way of testing at compile time that      I've fixed the data, and added a kludgy way of testing at compile time that
877      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
878    
879  8.  Following on from 7, I added a similar kludge to check the length of the  8.  Following on from 7, I added a similar kludge to check the length of the
880      eint vector in pcreposix.c.      eint vector in pcreposix.c.
881    
882  9.  Error texts for pcre_compile() are held as one long string to avoid too  9.  Error texts for pcre_compile() are held as one long string to avoid too
883      much relocation at load time. To find a text, the string is searched,      much relocation at load time. To find a text, the string is searched,
884      counting zeros. There was no check for running off the end of the string,      counting zeros. There was no check for running off the end of the string,
885      which could happen if a new error number was added without updating the      which could happen if a new error number was added without updating the
886      string.      string.
887    
888  10. \K gave a compile-time error if it appeared in a lookbehind assersion.  10. \K gave a compile-time error if it appeared in a lookbehind assersion.
889    
890  11. \K was not working if it appeared in an atomic group or in a group that  11. \K was not working if it appeared in an atomic group or in a group that
891      was called as a "subroutine", or in an assertion. Perl 5.11 documents that      was called as a "subroutine", or in an assertion. Perl 5.11 documents that
892      \K is "not well defined" if used in an assertion. PCRE now accepts it if      \K is "not well defined" if used in an assertion. PCRE now accepts it if
893      the assertion is positive, but not if it is negative.      the assertion is positive, but not if it is negative.
894    
895  12. Change 11 fortuitously reduced the size of the stack frame used in the  12. Change 11 fortuitously reduced the size of the stack frame used in the
896      "match()" function of pcre_exec.c by one pointer. Forthcoming      "match()" function of pcre_exec.c by one pointer. Forthcoming
897      implementation of support for (*MARK) will need an extra pointer on the      implementation of support for (*MARK) will need an extra pointer on the
898      stack; I have reserved it now, so that the stack frame size does not      stack; I have reserved it now, so that the stack frame size does not
899      decrease.      decrease.
900    
901  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
902      item in branch that calls a recursion is a subroutine call - as in the      item in branch that calls a recursion is a subroutine call - as in the
903      second branch in the above example - was incorrectly given the compile-      second branch in the above example - was incorrectly given the compile-
904      time error "recursive call could loop indefinitely" because pcre_compile()      time error "recursive call could loop indefinitely" because pcre_compile()
905      was not correctly checking the subroutine for matching a non-empty string.      was not correctly checking the subroutine for matching a non-empty string.
906    
907  14. The checks for overrunning compiling workspace could trigger after an  14. The checks for overrunning compiling workspace could trigger after an
908      overrun had occurred. This is a "should never occur" error, but it can be      overrun had occurred. This is a "should never occur" error, but it can be
909      triggered by pathological patterns such as hundreds of nested parentheses.      triggered by pathological patterns such as hundreds of nested parentheses.
910      The checks now trigger 100 bytes before the end of the workspace.      The checks now trigger 100 bytes before the end of the workspace.
911    
912    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
913    
914    
915  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010

Legend:
Removed from v.505  
changed lines
  Added in v.931

  ViewVC Help
Powered by ViewVC 1.1.5