ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.517  
changed lines
  Added in v.969

  ViewVC Help
Powered by ViewVC 1.1.5