ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 200 by ph10, Wed Aug 1 09:10:40 2007 UTC revision 553 by ph10, Fri Oct 22 15:57:50 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 8.11 10-Oct-2010
5    ------------------------
7    1.  (*THEN) was not working properly if there were untried alternatives prior
8        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
9        backtracked to try for "b" instead of moving to the next alternative branch
10        at the same level (in this case, to look for "c"). The Perl documentation
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
14    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
15        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
16        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18        (*THEN).
20    3.  If \s appeared in a character class, it removed the VT character from
21        the class, even if it had been included by some previous item, for example
22        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
23        of \s, but is part of the POSIX "space" class.)
25    4.  A partial match never returns an empty string (because you can always
26        match an empty string at the end of the subject); however the checking for
27        an empty string was starting at the "start of match" point. This has been
28        changed to the "earliest inspected character" point, because the returned
29        data for a partial match starts at this character. This means that, for
30        example, /(?<=abc)def/ gives a partial match for the subject "abc"
31        (previously it gave "no match").
33    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
34        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
35        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
36        has an implication that the given string is incomplete (because a partial
37        match is preferred over a full match). For this reason, these items now
38        give a partial match in this situation. [Aside: previously, the one case
39        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
40        match rather than a full match, which was wrong by the old rules, but is
41        now correct.]
44    Version 8.10 25-Jun-2010
45    ------------------------
47    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
48        THEN.
50    2.  (*ACCEPT) was not working when inside an atomic group.
52    3.  Inside a character class, \B is treated as a literal by default, but
53        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
54        causes the error). The code is unchanged, but I tidied the documentation.
56    4.  Inside a character class, PCRE always treated \R and \X as literals,
57        whereas Perl faults them if its -w option is set. I have changed PCRE so
58        that it faults them when PCRE_EXTRA is set.
60    5.  Added support for \N, which always matches any character other than
61        newline. (It is the same as "." when PCRE_DOTALL is not set.)
63    6.  When compiling pcregrep with newer versions of gcc which may have
64        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
65        declared with attribute warn_unused_result" were given. Just casting the
66        result to (void) does not stop the warnings; a more elaborate fudge is
67        needed. I've used a macro to implement this.
69    7.  Minor change to pcretest.c to avoid a compiler warning.
71    8.  Added four artifical Unicode properties to help with an option to make
72        \s etc use properties (see next item). The new properties are: Xan
73        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
75    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
76        use Unicode properties. (*UCP) at the start of a pattern can be used to set
77        this option. Modified pcretest to add /W to test this facility. Added
78        REG_UCP to make it available via the POSIX interface.
80    10. Added --line-buffered to pcregrep.
82    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
83        studied, and the match started with a letter with a code point greater than
84        127 whose first byte was different to the first byte of the other case of
85        the letter, the other case of this starting letter was not recognized
86        (#976).
88    12. If a pattern that was studied started with a repeated Unicode property
89        test, for example, \p{Nd}+, there was the theoretical possibility of
90        setting up an incorrect bitmap of starting bytes, but fortunately it could
91        not have actually happened in practice until change 8 above was made (it
92        added property types that matched character-matching opcodes).
94    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
95        possible starting bytes for non-anchored patterns.
97    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
98        \R, and also a number of cases that involve Unicode properties, both
99        explicit and implicit when PCRE_UCP is set.
101    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
102        input, it could crash or give wrong results if characters with values
103        greater than 0xc0 were present in the subject string. (Detail: it assumed
104        UTF-8 input when processing these items.)
106    16. Added a lot of (int) casts to avoid compiler warnings in systems where
107        size_t is 64-bit (#991).
109    17. Added a check for running out of memory when PCRE is compiled with
110        --disable-stack-for-recursion (#990).
112    18. If the last data line in a file for pcretest does not have a newline on
113        the end, a newline was missing in the output.
115    19. The default pcre_chartables.c file recognizes only ASCII characters (values
116        less than 128) in its various bitmaps. However, there is a facility for
117        generating tables according to the current locale when PCRE is compiled. It
118        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
119        characters, are recognized by isspace() and therefore were getting set in
120        these tables, and indeed these tables seem to approximate to ISO 8859. This
121        caused a problem in UTF-8 mode when pcre_study() was used to create a list
122        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
123        which of course cannot start UTF-8 characters. I have changed the code so
124        that only real ASCII characters (less than 128) and the correct starting
125        bytes for UTF-8 encodings are set for characters greater than 127 when in
126        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
127        altogether.)
129    20. Added the /T option to pcretest so as to be able to run tests with non-
130        standard character tables, thus making it possible to include the tests
131        used for 19 above in the standard set of tests.
133    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
134        reference to a subpattern the other side of a comment that contains an
135        opening parenthesis caused either an internal compiling error, or a
136        reference to the wrong subpattern.
139    Version 8.02 19-Mar-2010
140    ------------------------
142    1.  The Unicode data tables have been updated to Unicode 5.2.0.
144    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
145        configured.
147    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
148        original author of that file, following a query about its status.
150    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
151        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
153    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
154        quantifier applied to a forward-referencing subroutine call, could compile
155        incorrect code or give the error "internal error: previously-checked
156        referenced subpattern not found".
158    6.  Both MS Visual Studio and Symbian OS have problems with initializing
159        variables to point to external functions. For these systems, therefore,
160        pcre_malloc etc. are now initialized to local functions that call the
161        relevant global functions.
163    7.  There were two entries missing in the vectors called coptable and poptable
164        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
165        I've fixed the data, and added a kludgy way of testing at compile time that
166        the lengths are correct (equal to the number of opcodes).
168    8.  Following on from 7, I added a similar kludge to check the length of the
169        eint vector in pcreposix.c.
171    9.  Error texts for pcre_compile() are held as one long string to avoid too
172        much relocation at load time. To find a text, the string is searched,
173        counting zeros. There was no check for running off the end of the string,
174        which could happen if a new error number was added without updating the
175        string.
177    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
179    11. \K was not working if it appeared in an atomic group or in a group that
180        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
181        \K is "not well defined" if used in an assertion. PCRE now accepts it if
182        the assertion is positive, but not if it is negative.
184    12. Change 11 fortuitously reduced the size of the stack frame used in the
185        "match()" function of pcre_exec.c by one pointer. Forthcoming
186        implementation of support for (*MARK) will need an extra pointer on the
187        stack; I have reserved it now, so that the stack frame size does not
188        decrease.
190    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
191        item in branch that calls a recursion is a subroutine call - as in the
192        second branch in the above example - was incorrectly given the compile-
193        time error "recursive call could loop indefinitely" because pcre_compile()
194        was not correctly checking the subroutine for matching a non-empty string.
196    14. The checks for overrunning compiling workspace could trigger after an
197        overrun had occurred. This is a "should never occur" error, but it can be
198        triggered by pathological patterns such as hundreds of nested parentheses.
199        The checks now trigger 100 bytes before the end of the workspace.
201    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
204    Version 8.01 19-Jan-2010
205    ------------------------
207    1.  If a pattern contained a conditional subpattern with only one branch (in
208        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
209        computed the wrong minimum data length (which is of course zero for such
210        subpatterns). This could cause incorrect "no match" results.
212    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
213        the pattern is reset in the first branch, pcre_compile() failed with
214        "internal error: code overflow at offset...". This happened only when
215        the reset was to the original external option setting. (An optimization
216        abstracts leading options settings into an external setting, which was the
217        cause of this.)
219    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
220        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
221        assertion pattern did not match (meaning that the assertion was true), it
222        was incorrectly treated as false if the SKIP had been reached during the
223        matching. This also applied to assertions used as conditions.
225    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
226        assertion subpattern, including such a pattern used as a condition,
227        unpredictable results occurred, instead of the error return
230    5.  The C++ GlobalReplace function was not working like Perl for the special
231        situation when an empty string is matched. It now does the fancy magic
232        stuff that is necessary.
234    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
235        removed. (These were left over from very, very early versions of PCRE.)
237    7.  Some cosmetic changes to the code to make life easier when compiling it
238        as part of something else:
240        (a) Change DEBUG to PCRE_DEBUG.
242        (b) In pcre_compile(), rename the member of the "branch_chain" structure
243            called "current" as "current_branch", to prevent a collision with the
244            Linux macro when compiled as a kernel module.
246        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
247            prevent a collision with the Linux macro when compiled as a kernel
248            module.
250    8.  In pcre_compile() there are some checks for integer overflows that used to
251        cast potentially large values to (double). This has been changed to that
252        when building, a check for int64_t is made, and if it is found, it is used
253        instead, thus avoiding the use of floating point arithmetic. (There is no
254        other use of FP in PCRE.) If int64_t is not found, the fallback is to
255        double.
257    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
258        2005 (difference between two addresses compared to an unsigned value).
260    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
261        custom one, because of the following reported problem in Windows:
263          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
264              under Win32.
265          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
266              therefore missing the function definition.
267          - The compiler thus generates a "C" signature for the test function.
268          - The linker fails to find the "C" function.
269          - PCRE fails to configure if asked to do so against libbz2.
271    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
272        messages were output:
274          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
275          rerunning libtoolize, to keep the correct libtool macros in-tree.
276          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
278        I have done both of these things.
280    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
281        most of the time, it *can* run out if it is given a pattern that contains a
282        runaway infinite recursion. I updated the discussion in the pcrestack man
283        page.
285    13. Now that we have gone to the x.xx style of version numbers, the minor
286        version may start with zero. Using 08 or 09 is a bad idea because users
287        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
288        interpreted as invalid octal numbers. I've updated the previous comment in
289        configure.ac, and also added a check that gives an error if 08 or 09 are
290        used.
292    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
293        causing partial matching to fail when the end of the subject matched \W
294        in a UTF-8 pattern where \W was quantified with a minimum of 3.
296    15. There were some discrepancies between the declarations in pcre_internal.h
297        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
298        their definitions. The declarations used "const uschar *" and the
299        definitions used USPTR. Even though USPTR is normally defined as "const
300        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
301        reported that: "This difference in casting confuses some C++ compilers, for
302        example, SunCC recognizes above declarations as different functions and
303        generates broken code for hbpcre." I have changed the declarations to use
304        USPTR.
306    16. GNU libtool is named differently on some systems. The autogen.sh script now
307        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
308        (FreeBSD).
310    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
311        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
312        comment: "Figure out how to create a longlong from a string: strtoll and
313        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
314        instance, but it only takes 2 args instead of 3!"
316    18. A subtle bug concerned with back references has been fixed by a change of
317        specification, with a corresponding code fix. A pattern such as
318        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
319        refers, was giving matches when it shouldn't. For example, xa=xaaa would
320        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
321        same bug. Such groups have to be quantified to be useful, or contained
322        inside another quantified group. (If there's no repetition, the reference
323        can never match.) The problem arises because, having left the group and
324        moved on to the rest of the pattern, a later failure that backtracks into
325        the group uses the captured value from the final iteration of the group
326        rather than the correct earlier one. I have fixed this in PCRE by forcing
327        any group that contains a reference to itself to be an atomic group; that
328        is, there cannot be any backtracking into it once it has completed. This is
329        similar to recursive and subroutine calls.
332    Version 8.00 19-Oct-09
333    ----------------------
335    1.  The table for translating pcre_compile() error codes into POSIX error codes
336        was out-of-date, and there was no check on the pcre_compile() error code
337        being within the table. This could lead to an OK return being given in
338        error.
340    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
341        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
342        in a Windows environment.
344    3.  The pcregrep --count option prints the count for each file even when it is
345        zero, as does GNU grep. However, pcregrep was also printing all files when
346        --files-with-matches was added. Now, when both options are given, it prints
347        counts only for those files that have at least one match. (GNU grep just
348        prints the file name in this circumstance, but including the count seems
349        more useful - otherwise, why use --count?) Also ensured that the
350        combination -clh just lists non-zero counts, with no names.
352    4.  The long form of the pcregrep -F option was incorrectly implemented as
353        --fixed_strings instead of --fixed-strings. This is an incompatible change,
354        but it seems right to fix it, and I didn't think it was worth preserving
355        the old behaviour.
357    5.  The command line items --regex=pattern and --regexp=pattern were not
358        recognized by pcregrep, which required --regex pattern or --regexp pattern
359        (with a space rather than an '='). The man page documented the '=' forms,
360        which are compatible with GNU grep; these now work.
362    6.  No libpcreposix.pc file was created for pkg-config; there was just
363        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
365    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
366        when UCP support is not needed, by modifying the Python script that
367        generates it from Unicode data files. This should not matter if the module
368        is correctly used as a library, but I received one complaint about 50K of
369        unwanted data. My guess is that the person linked everything into his
370        program rather than using a library. Anyway, it does no harm.
372    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
373        was a minimum greater than 1 for a wide character in a possessive
374        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
375        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
376        character. Chaos in the form of incorrect output or a compiling loop could
377        result.
379    9.  The restrictions on what a pattern can contain when partial matching is
380        requested for pcre_exec() have been removed. All patterns can now be
381        partially matched by this function. In addition, if there are at least two
382        slots in the offset vector, the offset of the earliest inspected character
383        for the match and the offset of the end of the subject are set in them when
384        PCRE_ERROR_PARTIAL is returned.
386    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
387        synonymous with PCRE_PARTIAL, for backwards compatibility, and
388        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
389        and may be more useful for multi-segment matching.
391    11. Partial matching with pcre_exec() is now more intuitive. A partial match
392        used to be given if ever the end of the subject was reached; now it is
393        given only if matching could not proceed because another character was
394        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
395        string "Z", which now yields "no match" instead of "partial match". In the
396        case of pcre_dfa_exec(), "no match" is given if every matching path for the
397        final character ended with (*FAIL).
399    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
400        if the pattern had a "must contain" character that was already found in the
401        earlier partial match, unless partial matching was again requested. For
402        example, with the pattern /dog.(body)?/, the "must contain" character is
403        "g". If the first part-match was for the string "dog", restarting with
404        "sbody" failed. This bug has been fixed.
406    13. The string returned by pcre_dfa_exec() after a partial match has been
407        changed so that it starts at the first inspected character rather than the
408        first character of the match. This makes a difference only if the pattern
409        starts with a lookbehind assertion or \b or \B (\K is not supported by
410        pcre_dfa_exec()). It's an incompatible change, but it makes the two
411        matching functions compatible, and I think it's the right thing to do.
413    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
414        so that the demonstration program is easily available in environments where
415        PCRE has not been installed from source.
417    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
418        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
419        library.
421    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
422        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
423        is not the first non-POSIX option to be added. Clearly some people find
424        these options useful.
426    17. If a caller to the POSIX matching function regexec() passes a non-zero
427        value for nmatch with a NULL value for pmatch, the value of
428        nmatch is forced to zero.
430    18. RunGrepTest did not have a test for the availability of the -u option of
431        the diff command, as RunTest does. It now checks in the same way as
432        RunTest, and also checks for the -b option.
434    19. If an odd number of negated classes containing just a single character
435        interposed, within parentheses, between a forward reference to a named
436        subpattern and the definition of the subpattern, compilation crashed with
437        an internal error, complaining that it could not find the referenced
438        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
439        [The bug was that it was starting one character too far in when skipping
440        over the character class, thus treating the ] as data rather than
441        terminating the class. This meant it could skip too much.]
443    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
444        /g option in pcretest when the pattern contains \K, which makes it possible
445        to have an empty string match not at the start, even when the pattern is
446        anchored. Updated pcretest and pcredemo to use this option.
448    21. If the maximum number of capturing subpatterns in a recursion was greater
449        than the maximum at the outer level, the higher number was returned, but
450        with unset values at the outer level. The correct (outer level) value is
451        now given.
453    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
454        PCRE did not set those parentheses (unlike Perl). I have now found a way to
455        make it do so. The string so far is captured, making this feature
456        compatible with Perl.
458    23. The tests have been re-organized, adding tests 11 and 12, to make it
459        possible to check the Perl 5.10 features against Perl 5.10.
461    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
462        pattern matches a fixed length string. PCRE did not allow this; now it
463        does. Neither allows recursion.
465    25. I finally figured out how to implement a request to provide the minimum
466        length of subject string that was needed in order to match a given pattern.
467        (It was back references and recursion that I had previously got hung up
468        on.) This code has now been added to pcre_study(); it finds a lower bound
469        to the length of subject needed. It is not necessarily the greatest lower
470        bound, but using it to avoid searching strings that are too short does give
471        some useful speed-ups. The value is available to calling programs via
472        pcre_fullinfo().
474    26. While implementing 25, I discovered to my embarrassment that pcretest had
475        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
476        study optimizations had never been tested with that matching function.
477        Oops. What is worse, even when it was passed study data, there was a bug in
478        pcre_dfa_exec() that meant it never actually used it. Double oops. There
479        were also very few tests of studied patterns with pcre_dfa_exec().
481    27. If (?| is used to create subpatterns with duplicate numbers, they are now
482        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
483        on the other side of the coin, they are no longer allowed to have different
484        names, because these cannot be distinguished in PCRE, and this has caused
485        confusion. (This is a difference from Perl.)
487    28. When duplicate subpattern names are present (necessarily with different
488        numbers, as required by 27 above), and a test is made by name in a
489        conditional pattern, either for a subpattern having been matched, or for
490        recursion in such a pattern, all the associated numbered subpatterns are
491        tested, and the overall condition is true if the condition is true for any
492        one of them. This is the way Perl works, and is also more like the way
493        testing by number works.
496    Version 7.9 11-Apr-09
497    ---------------------
499    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
500        (pcretest), all targets were linked against these libraries. This included
501        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
502        libraries. This caused unwanted dependencies to be created. This problem
503        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
504        pcretest is linked with readline.
506    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
507        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
508        moved outside it again, because FALSE and TRUE are already defined in AIX,
509        but BOOL is not.
511    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
512        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
514    4.  The pcregrep documentation said spaces were inserted as well as colons (or
515        hyphens) following file names and line numbers when outputting matching
516        lines. This is not true; no spaces are inserted. I have also clarified the
517        wording for the --colour (or --color) option.
519    5.  In pcregrep, when --colour was used with -o, the list of matching strings
520        was not coloured; this is different to GNU grep, so I have changed it to be
521        the same.
523    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
524        each matching line was coloured. Now it goes on to look for further matches
525        of any of the test patterns, which is the same behaviour as GNU grep.
527    7.  A pattern that could match an empty string could cause pcregrep to loop; it
528        doesn't make sense to accept an empty string match in pcregrep, so I have
529        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
530        seems to be how GNU grep behaves.
532    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
533        start or after a newline", because the conditional assertion was not being
534        correctly handled. The rule now is that both the assertion and what follows
535        in the first alternative must satisfy the test.
537    9.  If auto-callout was enabled in a pattern with a conditional group whose
538        condition was an assertion, PCRE could crash during matching, both with
539        pcre_exec() and pcre_dfa_exec().
541    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
542        used for matching.
544    11. Unicode property support in character classes was not working for
545        characters (bytes) greater than 127 when not in UTF-8 mode.
547    12. Added the -M command line option to pcretest.
549    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
551    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
553    16. Added comments and documentation about mis-use of no_arg in the C++
554        wrapper.
556    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
557        from Martin Jerabek that uses macro names for all relevant character and
558        string constants.
560    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
561        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
562        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
563        these, but not everybody uses configure.
565    19. A conditional group that had only one branch was not being correctly
566        recognized as an item that could match an empty string. This meant that an
567        enclosing group might also not be so recognized, causing infinite looping
568        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
569        with the subject "ab", where knowledge that the repeated group can match
570        nothing is needed in order to break the loop.
572    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
573        exec(), but without supplying a callout function, matching went wrong.
575    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
576        leak if the size of the offset vector was greater than 30. When the vector
577        is smaller, the saved offsets during recursion go onto a local stack
578        vector, but for larger vectors malloc() is used. It was failing to free
579        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
580        error, in fact).
582    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
583        heapframe that is used only when UTF-8 support is enabled. This caused no
584        problem, but was untidy.
586    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
587        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
588        included within another project.
590    24. Steven Van Ingelgem's patches to add more options to the CMake support,
591        slightly modified by me:
593          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
594              not building pcregrep.
596          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
597              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
599    25. Forward references, both numeric and by name, in patterns that made use of
600        duplicate group numbers, could behave incorrectly or give incorrect errors,
601        because when scanning forward to find the reference group, PCRE was not
602        taking into account the duplicate group numbers. A pattern such as
603        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
605    26. Changed a few more instances of "const unsigned char *" to USPTR, making
606        the feature of a custom pointer more persuasive (as requested by a user).
608    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
609        pcretest.c, inside #ifndefs, because it seems they are sometimes already
610        pre-defined.
612    28. Added support for (*UTF8) at the start of a pattern.
614    29. Arrange for flags added by the "release type" setting in CMake to be shown
615        in the configuration summary.
618    Version 7.8 05-Sep-08
619    ---------------------
621    1.  Replaced UCP searching code with optimized version as implemented for Ad
622        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
623        stage table and inline lookup instead of a function, giving speed ups of 2
624        to 5 times on some simple patterns that I tested. Permission was given to
625        distribute the MultiStage2.py script that generates the tables (it's not in
626        the tarball, but is in the Subversion repository).
628    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
629        scripts.
631    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
632        a group with a zero qualifier. The result of the study could be incorrect,
633        or the function might crash, depending on the pattern.
635    4.  Caseless matching was not working for non-ASCII characters in back
636        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
637        It now works when Unicode Property Support is available.
639    5.  In pcretest, an escape such as \x{de} in the data was always generating
640        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
641        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
642        truncation.
644    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
646    7.  Added two (int) casts to pcregrep when printing the difference of two
647        pointers, in case they are 64-bit values.
649    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
650        test 2 if it fails.
652    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
653        and a #define of that name to empty if it is not externally set. This is to
654        allow users of MSVC to set it if necessary.
656    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
657        the convenience functions in the pcre_get.c source file.
659    11. An option change at the start of a pattern that had top-level alternatives
660        could cause overwriting and/or a crash. This command provoked a crash in
661        some environments:
663          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
665        This potential security problem was recorded as CVE-2008-2371.
667    12. For a pattern where the match had to start at the beginning or immediately
668        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
669        pcre_dfa_exec() could read past the end of the passed subject if there was
670        no match. To help with detecting such bugs (e.g. with valgrind), I modified
671        pcretest so that it places the subject at the end of its malloc-ed buffer.
673    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
674        exec() might read past the end of the data buffer in UTF-8 mode.
676    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
677        the data contained the byte 0x85 as part of a UTF-8 character within its
678        first line. This applied both to normal and DFA matching.
680    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
681        /^[^d]*?$/8 failed to match "abc".
683    16. Added a missing copyright notice to pcrecpp_internal.h.
685    17. Make it more clear in the documentation that values returned from
686        pcre_exec() in ovector are byte offsets, not character counts.
688    18. Tidied a few places to stop certain compilers from issuing warnings.
690    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
691        supplied by Stefan Weber. I made a further small update for 7.8 because
692        there is a change of source arrangements: the pcre_searchfuncs.c module is
693        replaced by pcre_ucd.c.
696    Version 7.7 07-May-08
697    ---------------------
699    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
700        a string to a long long, pretend we don't even have a long long." This is
701        done by checking for the strtoq, strtoll, and _strtoi64 functions.
703    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
704        pre-7.6 versions, which defined a global no_arg variable instead of putting
705        it in the RE class. (See also #8 below.)
707    3.  Remove a line of dead code, identified by coverity and reported by Nuno
708        Lopes.
710    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
712        (1) The include/exclude patterns were being applied to the whole pathnames
713            of files, instead of just to the final components.
715        (2) If there was more than one level of directory, the subdirectories were
716            skipped unless they satisfied the include/exclude conditions. This is
717            inconsistent with GNU grep (and could even be seen as contrary to the
718            pcregrep specification - which I improved to make it absolutely clear).
719            The action now is always to scan all levels of directory, and just
720            apply the include/exclude patterns to regular files.
722    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
723        --exclude_dir in the tests to avoid scanning .svn directories.
725    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
726        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
727        doesn't support NULs in patterns.
729    7.  Added some missing "const"s to declarations of static tables in
730        pcre_compile.c and pcre_dfa_exec.c.
732    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
733        caused by fix #2  above. (Subsequently also a second patch to fix the
734        first patch. And a third patch - this was a messy problem.)
736    9.  Applied Craig's patch to remove the use of push_back().
738    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
739        matching function regexec().
741    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
742        which, however, unlike Perl's \g{...}, are subroutine calls, not back
743        references. PCRE supports relative numbers with this syntax (I don't think
744        Oniguruma does).
746    12. Previously, a group with a zero repeat such as (...){0} was completely
747        omitted from the compiled regex. However, this means that if the group
748        was called as a subroutine from elsewhere in the pattern, things went wrong
749        (an internal error was given). Such groups are now left in the compiled
750        pattern, with a new opcode that causes them to be skipped at execution
751        time.
753    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
754        to the way PCRE behaves:
756        (a) A lone ] character is dis-allowed (Perl treats it as data).
758        (b) A back reference to an unmatched subpattern matches an empty string
759            (Perl fails the current match path).
761        (c) A data ] in a character class must be notated as \] because if the
762            first data character in a class is ], it defines an empty class. (In
763            Perl it is not possible to have an empty class.) The empty class []
764            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
765            The negative empty class [^] matches any one character, independently
766            of the DOTALL setting.
768    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
769        non-existent subpattern following a character class starting with ']' and
770        containing () gave an internal compiling error instead of "reference to
771        non-existent subpattern". Fortunately, when the pattern did exist, the
772        compiled code was correct. (When scanning forwards to check for the
773        existencd of the subpattern, it was treating the data ']' as terminating
774        the class, so got the count wrong. When actually compiling, the reference
775        was subsequently set up correctly.)
777    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
778        it was being rejected as not supported by pcre_dfa_exec(), even though
779        other assertions are supported. I have made pcre_dfa_exec() support
780        (*FAIL).
782    16. The implementation of 13c above involved the invention of a new opcode,
783        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
784        cannot be changed at match time, I realized I could make a small
785        improvement to matching performance by compiling OP_ALLANY instead of
786        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
787        on the OP_ANY path.
789    17. Compiling pcretest on Windows with readline support failed without the
790        following two fixes: (1) Make the unistd.h include conditional on
791        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
793    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
794        ncurses library to be included for pcretest when ReadLine support is
795        requested, but also to allow for it to be overridden. This patch came from
796        Daniel Bergström.
798    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
799        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
800        any errors with the current Unicode tables. Thanks to Peter Kankowski for
801        spotting this.
804    Version 7.6 28-Jan-08
805    ---------------------
807    1.  A character class containing a very large number of characters with
808        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
809        overflow.
811    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
812        HAVE_LONG_LONG is not defined.
814    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
815        bring them up to date and include new features. This patch includes:
817        - Fixed PH's badly added libz and libbz2 support.
818        - Fixed a problem with static linking.
819        - Added pcredemo. [But later removed - see 7 below.]
820        - Fixed dftables problem and added an option.
821        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
822            HAVE_LONG_LONG.
823        - Added readline support for pcretest.
824        - Added an listing of the option settings after cmake has run.
826    4.  A user submitted a patch to Makefile that makes it easy to create
827        "pcre.dll" under mingw when using Configure/Make. I added stuff to
828        Makefile.am that cause it to include this special target, without
829        affecting anything else. Note that the same mingw target plus all
830        the other distribution libraries and programs are now supported
831        when configuring with CMake (see 6 below) instead of with
832        Configure/Make.
834    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
835        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
836        exported in the Windows port". It has not yet been confirmed that the patch
837        solves the problem, but it does no harm.
839    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
840        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
841        with CMake, and also correct the comment about stack recursion.
843    7.  Remove the automatic building of pcredemo from the ./configure system and
844        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
845        of a program that users should build themselves after PCRE is installed, so
846        building it automatically is not really right. What is more, it gave
847        trouble in some build environments.
849    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
852    Version 7.5 10-Jan-08
853    ---------------------
855    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
856        values in parens when parsing an RE using the C++ wrapper."
858    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
859        Characters greater than 255 were excluded from the class instead of being
860        included.
862    3.  The same bug as (2) above applied to negated POSIX classes such as
863        [:^space:].
865    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
866        defined or documented. It seems to have been a typo for PCRE_STATIC, so
867        I have changed it.
869    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
870        first named subpattern) and a construct such as (?&a) would reference the
871        first named subpattern whose name started with "a" (in other words, the
872        length check was missing). Both these problems are fixed. "Subpattern name
873        expected" is now given for (?&) (a zero-length name), and this patch also
874        makes it give the same error for \k'' (previously it complained that that
875        was a reference to a non-existent subpattern).
877    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
878        this is right because (?- can be followed by option settings as well as by
879        digits. I have, however, made the messages clearer.
881    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
882        than the number used in the conditional) now cause a compile-time error.
883        This is actually not compatible with Perl, which accepts such patterns, but
884        treats the conditional as always being FALSE (as PCRE used to), but it
885        seems to me that giving a diagnostic is better.
887    8.  Change "alphameric" to the more common word "alphanumeric" in comments
888        and messages.
890    9.  Fix two occurrences of "backslash" in comments that should have been
891        "backspace".
893    10. Remove two redundant lines of code that can never be obeyed (their function
894        was moved elsewhere).
896    11. The program that makes PCRE's Unicode character property table had a bug
897        which caused it to generate incorrect table entries for sequences of
898        characters that have the same character type, but are in different scripts.
899        It amalgamated them into a single range, with the script of the first of
900        them. In other words, some characters were in the wrong script. There were
901        thirteen such cases, affecting characters in the following ranges:
903          U+002b0 - U+002c1
904          U+0060c - U+0060d
905          U+0061e - U+00612
906          U+0064b - U+0065e
907          U+0074d - U+0076d
908          U+01800 - U+01805
909          U+01d00 - U+01d77
910          U+01d9b - U+01dbf
911          U+0200b - U+0200f
912          U+030fc - U+030fe
913          U+03260 - U+0327f
914          U+0fb46 - U+0fbb1
915          U+10450 - U+1049d
917    12. The -o option (show only the matching part of a line) for pcregrep was not
918        compatible with GNU grep in that, if there was more than one match in a
919        line, it showed only the first of them. It now behaves in the same way as
920        GNU grep.
922    13. If the -o and -v options were combined for pcregrep, it printed a blank
923        line for every non-matching line. GNU grep prints nothing, and pcregrep now
924        does the same. The return code can be used to tell if there were any
925        non-matching lines.
927    14. Added --file-offsets and --line-offsets to pcregrep.
929    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
930        infinitely looping recursion. The bug was that positive lookaheads were not
931        being skipped when checking for a possible empty match (negative lookaheads
932        and both kinds of lookbehind were skipped).
934    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
935        inclusion of <windows.h> to before rather than after the definition of
936        INVALID_FILE_ATTRIBUTES (patch from David Byron).
938    17. Specifying a possessive quantifier with a specific limit for a Unicode
939        character property caused pcre_compile() to compile bad code, which led at
940        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
941        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
942        caused the error; without that there was no problem.
944    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
946    19. Added --enable-pcretest-libreadline.
948    20. In pcrecpp.cc, the variable 'count' was incremented twice in
949        RE::GlobalReplace(). As a result, the number of replacements returned was
950        double what it should be. I removed one of the increments, but Craig sent a
951        later patch that removed the other one (the right fix) and added unit tests
952        that check the return values (which was not done before).
954    21. Several CMake things:
956        (1) Arranged that, when cmake is used on Unix, the libraries end up with
957            the names libpcre and libpcreposix, not just pcre and pcreposix.
959        (2) The above change means that pcretest and pcregrep are now correctly
960            linked with the newly-built libraries, not previously installed ones.
964    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
965        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
966        UTF-8 newline character). The key issue is that the pattern starts .*;
967        this means that the match must be either at the beginning, or after a
968        newline. The bug was in the code for advancing after a failed match and
969        checking that the new position followed a newline. It was not taking
970        account of UTF-8 characters correctly.
972    23. PCRE was behaving differently from Perl in the way it recognized POSIX
973        character classes. PCRE was not treating the sequence [:...:] as a
974        character class unless the ... were all letters. Perl, however, seems to
975        allow any characters between [: and :], though of course it rejects as
976        unknown any "names" that contain non-letters, because all the known class
977        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
978        for example, whereas PCRE did not - it did not recognize a POSIX character
979        class. This seemed a bit dangerous, so the code has been changed to be
980        closer to Perl. The behaviour is not identical to Perl, because PCRE will
981        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
982        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
983        Perl does, and where it didn't before.
985    24. Rewrite so as to remove the single use of %n from pcregrep because in some
986        Windows environments %n is disabled by default.
989    Version 7.4 21-Sep-07
990    ---------------------
992    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
993        means that a class such as [\s] counted as "explicit reference to CR or
994        LF". That isn't really right - the whole point of the change was to try to
995        help when there was an actual mention of one of the two characters. So now
996        the change happens only if \r or \n (or a literal CR or LF) character is
997        encountered.
999    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1000        of both had grown to the point where there were only 3 bits left.
1001        Fortunately, there was spare space in the data structure, and so I have
1002        moved the internal flags into a new 16-bit field to free up more option
1003        bits.
1005    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1006        but did not set the internal JCHANGED flag - either of these is enough to
1007        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1008        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1009        start sets both bits.
1011    4.  Added options (at build time, compile time, exec time) to change \R from
1012        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1014    5.  doc/pcresyntax.html was missing from the distribution.
1016    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1017        compatibility, even though it is no longer used.
1019    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1020        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1021        windows.h file is present (where different names are used). [This was
1022        reversed later after testing - see 16 below.]
1024    8.  Changed all #include <config.h> to #include "config.h". There were also
1025        some further <pcre.h> cases that I changed to "pcre.h".
1027    9.  When pcregrep was used with the --colour option, it missed the line ending
1028        sequence off the lines that it output.
1030    10. It was pointed out to me that arrays of string pointers cause lots of
1031        relocations when a shared library is dynamically loaded. A technique of
1032        using a single long string with a table of offsets can drastically reduce
1033        these. I have refactored PCRE in four places to do this. The result is
1034        dramatic:
1036          Originally:                          290
1037          After changing UCP table:            187
1038          After changing error message table:   43
1039          After changing table of "verbs"       36
1040          After changing table of Posix names   22
1042        Thanks to the folks working on Gregex for glib for this insight.
1044    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1045        unicode-properties was also set.
1047    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1049    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1050        checked only for CRLF.
1052    14. Added casts to pcretest.c to avoid compiler warnings.
1054    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1056    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1057        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1058        entirely. This removes changes made in 7 above.
1060    17. The CMake files have been updated, and there is now more information about
1061        building with CMake in the NON-UNIX-USE document.
1064    Version 7.3 28-Aug-07
1065  ---------------------  ---------------------
1067   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 29  Version 7.3 05-Jul-07 Line 1089  Version 7.3 05-Jul-07
1089   4. Debugging: adjusted the names of opcodes for different kinds of parentheses   4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1090      in debug output.      in debug output.
1092   5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp   5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1093      unittest when running under MinGW.      long printing in the pcrecpp unittest when running under MinGW.
1095   6. ESC_K was left out of the EBCDIC table.   6. ESC_K was left out of the EBCDIC table.
# Line 53  Version 7.3 05-Jul-07 Line 1113  Version 7.3 05-Jul-07
1113      pcreposix and pcrecpp parts of the library. These were overlooked when this      pcreposix and pcrecpp parts of the library. These were overlooked when this
1114      problem was solved for the main library.      problem was solved for the main library.
1116     9. There were some crude static tests to avoid integer overflow when computing
1117        the size of patterns that contain repeated groups with explicit upper
1118        limits. As the maximum quantifier is 65535, the maximum group length was
1119        set at 30,000 so that the product of these two numbers did not overflow a
1120        32-bit integer. However, it turns out that people want to use groups that
1121        are longer than 30,000 bytes (though not repeat them that many times).
1122        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1123        made it possible to implement the integer overflow checks in a much more
1124        dynamic way, which I have now done. The artificial limitation on group
1125        length has been removed - we now have only the limit on the total length of
1126        the compiled pattern, which depends on the LINK_SIZE setting.
1128    10. Fixed a bug in the documentation for get/copy named substring when
1129        duplicate names are permitted. If none of the named substrings are set, the
1130        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1131        empty string.
1133    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1134        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1135        because the ] is interpreted as the first data character and the
1136        terminating ] is not found. PCRE has been made compatible with Perl in this
1137        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1138        cause memory overwriting.
1140    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1141        string has been matched (to stop an infinite loop). It was not recognizing
1142        a conditional subpattern that could match an empty string if that
1143        subpattern was within another subpattern. For example, it looped when
1144        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1145        condition was not nested. This bug has been fixed.
1147    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1148        past the start of the subject in the presence of bytes with the top bit
1149        set, for example "\x8aBCD".
1151    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1152        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1154    14. Optimized (?!) to (*FAIL).
1156    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1157        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1158        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1159        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1160        does: it's just the validity check that is more restrictive.
1162    16. Inserted checks for integer overflows during escape sequence (backslash)
1163        processing, and also fixed erroneous offset values for syntax errors during
1164        backslash processing.
1166    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1167        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1169    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1170        caused an overrun.
1172    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1173        something other than just ASCII characters) inside a group that had an
1174        unlimited repeat caused a loop at compile time (while checking to see
1175        whether the group could match an empty string).
1177    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1178        [\P{Any}] did so. (Error in the code for printing property names.)
1180    21. An orphan \E inside a character class could cause a crash.
1182    22. A repeated capturing bracket such as (A)? could cause a wild memory
1183        reference during compilation.
1185    23. There are several functions in pcre_compile() that scan along a compiled
1186        expression for various reasons (e.g. to see if it's fixed length for look
1187        behind). There were bugs in these functions when a repeated \p or \P was
1188        present in the pattern. These operators have additional parameters compared
1189        with \d, etc, and these were not being taken into account when moving along
1190        the compiled data. Specifically:
1192        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1193            length.
1195        (b) An item such as \pL+ within a repeated group could cause crashes or
1196            loops.
1198        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1199            "reference to non-existent subpattern" error.
1201        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1203    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1204        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1206    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1208    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1209        character were causing crashes (broken optimization).
1211    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1212        \p or \P) caused a compile-time loop.
1214    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1215        break. For example, the unstudied pattern [\r\n]A does not match the string
1216        "\r\nA" because change 7.0/46 below moves the current point on by two
1217        characters after failing to match at the start. However, the pattern \nA
1218        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1219        the same is true. There doesn't seem any very clean way out of this, but
1220        what I have chosen to do makes the common cases work: PCRE now takes note
1221        of whether there can be an explicit match for \r or \n anywhere in the
1222        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1223        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1224        pattern has explicit CR or LF references.
1226    29. Added (*CR) etc for changing newline setting at start of pattern.
1229  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
1230  ---------------------  ---------------------

Removed from v.200  
changed lines
  Added in v.553

  ViewVC Help
Powered by ViewVC 1.1.5