ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 122 by ph10, Mon Mar 12 15:10:25 2007 UTC revision 561 by ph10, Sat Oct 30 18:37:47 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-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.]
43    6.  There was a bug in the handling of #-introduced comments, recognized when
44        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
45        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
46        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
47        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
48        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
49        places in pcre_compile().
51    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
52        comments when looking ahead for named forward references to subpatterns,
53        the only newline sequence it recognized was NL. It now handles newlines
54        according to the set newline convention.
56    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
57        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
58        cater for a lack of strerror(). These oversights have been fixed.
60    9.  Added --match-limit and --recursion-limit to pcregrep.
63    Version 8.10 25-Jun-2010
64    ------------------------
66    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
67        THEN.
69    2.  (*ACCEPT) was not working when inside an atomic group.
71    3.  Inside a character class, \B is treated as a literal by default, but
72        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
73        causes the error). The code is unchanged, but I tidied the documentation.
75    4.  Inside a character class, PCRE always treated \R and \X as literals,
76        whereas Perl faults them if its -w option is set. I have changed PCRE so
77        that it faults them when PCRE_EXTRA is set.
79    5.  Added support for \N, which always matches any character other than
80        newline. (It is the same as "." when PCRE_DOTALL is not set.)
82    6.  When compiling pcregrep with newer versions of gcc which may have
83        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
84        declared with attribute warn_unused_result" were given. Just casting the
85        result to (void) does not stop the warnings; a more elaborate fudge is
86        needed. I've used a macro to implement this.
88    7.  Minor change to pcretest.c to avoid a compiler warning.
90    8.  Added four artifical Unicode properties to help with an option to make
91        \s etc use properties (see next item). The new properties are: Xan
92        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
94    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
95        use Unicode properties. (*UCP) at the start of a pattern can be used to set
96        this option. Modified pcretest to add /W to test this facility. Added
97        REG_UCP to make it available via the POSIX interface.
99    10. Added --line-buffered to pcregrep.
101    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
102        studied, and the match started with a letter with a code point greater than
103        127 whose first byte was different to the first byte of the other case of
104        the letter, the other case of this starting letter was not recognized
105        (#976).
107    12. If a pattern that was studied started with a repeated Unicode property
108        test, for example, \p{Nd}+, there was the theoretical possibility of
109        setting up an incorrect bitmap of starting bytes, but fortunately it could
110        not have actually happened in practice until change 8 above was made (it
111        added property types that matched character-matching opcodes).
113    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
114        possible starting bytes for non-anchored patterns.
116    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
117        \R, and also a number of cases that involve Unicode properties, both
118        explicit and implicit when PCRE_UCP is set.
120    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
121        input, it could crash or give wrong results if characters with values
122        greater than 0xc0 were present in the subject string. (Detail: it assumed
123        UTF-8 input when processing these items.)
125    16. Added a lot of (int) casts to avoid compiler warnings in systems where
126        size_t is 64-bit (#991).
128    17. Added a check for running out of memory when PCRE is compiled with
129        --disable-stack-for-recursion (#990).
131    18. If the last data line in a file for pcretest does not have a newline on
132        the end, a newline was missing in the output.
134    19. The default pcre_chartables.c file recognizes only ASCII characters (values
135        less than 128) in its various bitmaps. However, there is a facility for
136        generating tables according to the current locale when PCRE is compiled. It
137        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
138        characters, are recognized by isspace() and therefore were getting set in
139        these tables, and indeed these tables seem to approximate to ISO 8859. This
140        caused a problem in UTF-8 mode when pcre_study() was used to create a list
141        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
142        which of course cannot start UTF-8 characters. I have changed the code so
143        that only real ASCII characters (less than 128) and the correct starting
144        bytes for UTF-8 encodings are set for characters greater than 127 when in
145        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
146        altogether.)
148    20. Added the /T option to pcretest so as to be able to run tests with non-
149        standard character tables, thus making it possible to include the tests
150        used for 19 above in the standard set of tests.
152    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
153        reference to a subpattern the other side of a comment that contains an
154        opening parenthesis caused either an internal compiling error, or a
155        reference to the wrong subpattern.
158    Version 8.02 19-Mar-2010
159    ------------------------
161    1.  The Unicode data tables have been updated to Unicode 5.2.0.
163    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
164        configured.
166    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
167        original author of that file, following a query about its status.
169    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
170        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
172    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
173        quantifier applied to a forward-referencing subroutine call, could compile
174        incorrect code or give the error "internal error: previously-checked
175        referenced subpattern not found".
177    6.  Both MS Visual Studio and Symbian OS have problems with initializing
178        variables to point to external functions. For these systems, therefore,
179        pcre_malloc etc. are now initialized to local functions that call the
180        relevant global functions.
182    7.  There were two entries missing in the vectors called coptable and poptable
183        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
184        I've fixed the data, and added a kludgy way of testing at compile time that
185        the lengths are correct (equal to the number of opcodes).
187    8.  Following on from 7, I added a similar kludge to check the length of the
188        eint vector in pcreposix.c.
190    9.  Error texts for pcre_compile() are held as one long string to avoid too
191        much relocation at load time. To find a text, the string is searched,
192        counting zeros. There was no check for running off the end of the string,
193        which could happen if a new error number was added without updating the
194        string.
196    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
198    11. \K was not working if it appeared in an atomic group or in a group that
199        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
200        \K is "not well defined" if used in an assertion. PCRE now accepts it if
201        the assertion is positive, but not if it is negative.
203    12. Change 11 fortuitously reduced the size of the stack frame used in the
204        "match()" function of pcre_exec.c by one pointer. Forthcoming
205        implementation of support for (*MARK) will need an extra pointer on the
206        stack; I have reserved it now, so that the stack frame size does not
207        decrease.
209    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
210        item in branch that calls a recursion is a subroutine call - as in the
211        second branch in the above example - was incorrectly given the compile-
212        time error "recursive call could loop indefinitely" because pcre_compile()
213        was not correctly checking the subroutine for matching a non-empty string.
215    14. The checks for overrunning compiling workspace could trigger after an
216        overrun had occurred. This is a "should never occur" error, but it can be
217        triggered by pathological patterns such as hundreds of nested parentheses.
218        The checks now trigger 100 bytes before the end of the workspace.
220    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
223    Version 8.01 19-Jan-2010
224    ------------------------
226    1.  If a pattern contained a conditional subpattern with only one branch (in
227        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
228        computed the wrong minimum data length (which is of course zero for such
229        subpatterns). This could cause incorrect "no match" results.
231    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
232        the pattern is reset in the first branch, pcre_compile() failed with
233        "internal error: code overflow at offset...". This happened only when
234        the reset was to the original external option setting. (An optimization
235        abstracts leading options settings into an external setting, which was the
236        cause of this.)
238    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
239        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
240        assertion pattern did not match (meaning that the assertion was true), it
241        was incorrectly treated as false if the SKIP had been reached during the
242        matching. This also applied to assertions used as conditions.
244    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
245        assertion subpattern, including such a pattern used as a condition,
246        unpredictable results occurred, instead of the error return
249    5.  The C++ GlobalReplace function was not working like Perl for the special
250        situation when an empty string is matched. It now does the fancy magic
251        stuff that is necessary.
253    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
254        removed. (These were left over from very, very early versions of PCRE.)
256    7.  Some cosmetic changes to the code to make life easier when compiling it
257        as part of something else:
259        (a) Change DEBUG to PCRE_DEBUG.
261        (b) In pcre_compile(), rename the member of the "branch_chain" structure
262            called "current" as "current_branch", to prevent a collision with the
263            Linux macro when compiled as a kernel module.
265        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
266            prevent a collision with the Linux macro when compiled as a kernel
267            module.
269    8.  In pcre_compile() there are some checks for integer overflows that used to
270        cast potentially large values to (double). This has been changed to that
271        when building, a check for int64_t is made, and if it is found, it is used
272        instead, thus avoiding the use of floating point arithmetic. (There is no
273        other use of FP in PCRE.) If int64_t is not found, the fallback is to
274        double.
276    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
277        2005 (difference between two addresses compared to an unsigned value).
279    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
280        custom one, because of the following reported problem in Windows:
282          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
283              under Win32.
284          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
285              therefore missing the function definition.
286          - The compiler thus generates a "C" signature for the test function.
287          - The linker fails to find the "C" function.
288          - PCRE fails to configure if asked to do so against libbz2.
290    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
291        messages were output:
293          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
294          rerunning libtoolize, to keep the correct libtool macros in-tree.
295          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
297        I have done both of these things.
299    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
300        most of the time, it *can* run out if it is given a pattern that contains a
301        runaway infinite recursion. I updated the discussion in the pcrestack man
302        page.
304    13. Now that we have gone to the x.xx style of version numbers, the minor
305        version may start with zero. Using 08 or 09 is a bad idea because users
306        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
307        interpreted as invalid octal numbers. I've updated the previous comment in
308        configure.ac, and also added a check that gives an error if 08 or 09 are
309        used.
311    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
312        causing partial matching to fail when the end of the subject matched \W
313        in a UTF-8 pattern where \W was quantified with a minimum of 3.
315    15. There were some discrepancies between the declarations in pcre_internal.h
316        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
317        their definitions. The declarations used "const uschar *" and the
318        definitions used USPTR. Even though USPTR is normally defined as "const
319        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
320        reported that: "This difference in casting confuses some C++ compilers, for
321        example, SunCC recognizes above declarations as different functions and
322        generates broken code for hbpcre." I have changed the declarations to use
323        USPTR.
325    16. GNU libtool is named differently on some systems. The autogen.sh script now
326        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
327        (FreeBSD).
329    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
330        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
331        comment: "Figure out how to create a longlong from a string: strtoll and
332        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
333        instance, but it only takes 2 args instead of 3!"
335    18. A subtle bug concerned with back references has been fixed by a change of
336        specification, with a corresponding code fix. A pattern such as
337        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
338        refers, was giving matches when it shouldn't. For example, xa=xaaa would
339        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
340        same bug. Such groups have to be quantified to be useful, or contained
341        inside another quantified group. (If there's no repetition, the reference
342        can never match.) The problem arises because, having left the group and
343        moved on to the rest of the pattern, a later failure that backtracks into
344        the group uses the captured value from the final iteration of the group
345        rather than the correct earlier one. I have fixed this in PCRE by forcing
346        any group that contains a reference to itself to be an atomic group; that
347        is, there cannot be any backtracking into it once it has completed. This is
348        similar to recursive and subroutine calls.
351    Version 8.00 19-Oct-09
352    ----------------------
354    1.  The table for translating pcre_compile() error codes into POSIX error codes
355        was out-of-date, and there was no check on the pcre_compile() error code
356        being within the table. This could lead to an OK return being given in
357        error.
359    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
360        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
361        in a Windows environment.
363    3.  The pcregrep --count option prints the count for each file even when it is
364        zero, as does GNU grep. However, pcregrep was also printing all files when
365        --files-with-matches was added. Now, when both options are given, it prints
366        counts only for those files that have at least one match. (GNU grep just
367        prints the file name in this circumstance, but including the count seems
368        more useful - otherwise, why use --count?) Also ensured that the
369        combination -clh just lists non-zero counts, with no names.
371    4.  The long form of the pcregrep -F option was incorrectly implemented as
372        --fixed_strings instead of --fixed-strings. This is an incompatible change,
373        but it seems right to fix it, and I didn't think it was worth preserving
374        the old behaviour.
376    5.  The command line items --regex=pattern and --regexp=pattern were not
377        recognized by pcregrep, which required --regex pattern or --regexp pattern
378        (with a space rather than an '='). The man page documented the '=' forms,
379        which are compatible with GNU grep; these now work.
381    6.  No libpcreposix.pc file was created for pkg-config; there was just
382        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
384    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
385        when UCP support is not needed, by modifying the Python script that
386        generates it from Unicode data files. This should not matter if the module
387        is correctly used as a library, but I received one complaint about 50K of
388        unwanted data. My guess is that the person linked everything into his
389        program rather than using a library. Anyway, it does no harm.
391    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
392        was a minimum greater than 1 for a wide character in a possessive
393        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
394        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
395        character. Chaos in the form of incorrect output or a compiling loop could
396        result.
398    9.  The restrictions on what a pattern can contain when partial matching is
399        requested for pcre_exec() have been removed. All patterns can now be
400        partially matched by this function. In addition, if there are at least two
401        slots in the offset vector, the offset of the earliest inspected character
402        for the match and the offset of the end of the subject are set in them when
403        PCRE_ERROR_PARTIAL is returned.
405    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
406        synonymous with PCRE_PARTIAL, for backwards compatibility, and
407        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
408        and may be more useful for multi-segment matching.
410    11. Partial matching with pcre_exec() is now more intuitive. A partial match
411        used to be given if ever the end of the subject was reached; now it is
412        given only if matching could not proceed because another character was
413        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
414        string "Z", which now yields "no match" instead of "partial match". In the
415        case of pcre_dfa_exec(), "no match" is given if every matching path for the
416        final character ended with (*FAIL).
418    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
419        if the pattern had a "must contain" character that was already found in the
420        earlier partial match, unless partial matching was again requested. For
421        example, with the pattern /dog.(body)?/, the "must contain" character is
422        "g". If the first part-match was for the string "dog", restarting with
423        "sbody" failed. This bug has been fixed.
425    13. The string returned by pcre_dfa_exec() after a partial match has been
426        changed so that it starts at the first inspected character rather than the
427        first character of the match. This makes a difference only if the pattern
428        starts with a lookbehind assertion or \b or \B (\K is not supported by
429        pcre_dfa_exec()). It's an incompatible change, but it makes the two
430        matching functions compatible, and I think it's the right thing to do.
432    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
433        so that the demonstration program is easily available in environments where
434        PCRE has not been installed from source.
436    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
437        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
438        library.
440    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
441        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
442        is not the first non-POSIX option to be added. Clearly some people find
443        these options useful.
445    17. If a caller to the POSIX matching function regexec() passes a non-zero
446        value for nmatch with a NULL value for pmatch, the value of
447        nmatch is forced to zero.
449    18. RunGrepTest did not have a test for the availability of the -u option of
450        the diff command, as RunTest does. It now checks in the same way as
451        RunTest, and also checks for the -b option.
453    19. If an odd number of negated classes containing just a single character
454        interposed, within parentheses, between a forward reference to a named
455        subpattern and the definition of the subpattern, compilation crashed with
456        an internal error, complaining that it could not find the referenced
457        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
458        [The bug was that it was starting one character too far in when skipping
459        over the character class, thus treating the ] as data rather than
460        terminating the class. This meant it could skip too much.]
462    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
463        /g option in pcretest when the pattern contains \K, which makes it possible
464        to have an empty string match not at the start, even when the pattern is
465        anchored. Updated pcretest and pcredemo to use this option.
467    21. If the maximum number of capturing subpatterns in a recursion was greater
468        than the maximum at the outer level, the higher number was returned, but
469        with unset values at the outer level. The correct (outer level) value is
470        now given.
472    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
473        PCRE did not set those parentheses (unlike Perl). I have now found a way to
474        make it do so. The string so far is captured, making this feature
475        compatible with Perl.
477    23. The tests have been re-organized, adding tests 11 and 12, to make it
478        possible to check the Perl 5.10 features against Perl 5.10.
480    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
481        pattern matches a fixed length string. PCRE did not allow this; now it
482        does. Neither allows recursion.
484    25. I finally figured out how to implement a request to provide the minimum
485        length of subject string that was needed in order to match a given pattern.
486        (It was back references and recursion that I had previously got hung up
487        on.) This code has now been added to pcre_study(); it finds a lower bound
488        to the length of subject needed. It is not necessarily the greatest lower
489        bound, but using it to avoid searching strings that are too short does give
490        some useful speed-ups. The value is available to calling programs via
491        pcre_fullinfo().
493    26. While implementing 25, I discovered to my embarrassment that pcretest had
494        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
495        study optimizations had never been tested with that matching function.
496        Oops. What is worse, even when it was passed study data, there was a bug in
497        pcre_dfa_exec() that meant it never actually used it. Double oops. There
498        were also very few tests of studied patterns with pcre_dfa_exec().
500    27. If (?| is used to create subpatterns with duplicate numbers, they are now
501        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
502        on the other side of the coin, they are no longer allowed to have different
503        names, because these cannot be distinguished in PCRE, and this has caused
504        confusion. (This is a difference from Perl.)
506    28. When duplicate subpattern names are present (necessarily with different
507        numbers, as required by 27 above), and a test is made by name in a
508        conditional pattern, either for a subpattern having been matched, or for
509        recursion in such a pattern, all the associated numbered subpatterns are
510        tested, and the overall condition is true if the condition is true for any
511        one of them. This is the way Perl works, and is also more like the way
512        testing by number works.
515    Version 7.9 11-Apr-09
516    ---------------------
518    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
519        (pcretest), all targets were linked against these libraries. This included
520        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
521        libraries. This caused unwanted dependencies to be created. This problem
522        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
523        pcretest is linked with readline.
525    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
526        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
527        moved outside it again, because FALSE and TRUE are already defined in AIX,
528        but BOOL is not.
530    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
531        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
533    4.  The pcregrep documentation said spaces were inserted as well as colons (or
534        hyphens) following file names and line numbers when outputting matching
535        lines. This is not true; no spaces are inserted. I have also clarified the
536        wording for the --colour (or --color) option.
538    5.  In pcregrep, when --colour was used with -o, the list of matching strings
539        was not coloured; this is different to GNU grep, so I have changed it to be
540        the same.
542    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
543        each matching line was coloured. Now it goes on to look for further matches
544        of any of the test patterns, which is the same behaviour as GNU grep.
546    7.  A pattern that could match an empty string could cause pcregrep to loop; it
547        doesn't make sense to accept an empty string match in pcregrep, so I have
548        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
549        seems to be how GNU grep behaves.
551    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
552        start or after a newline", because the conditional assertion was not being
553        correctly handled. The rule now is that both the assertion and what follows
554        in the first alternative must satisfy the test.
556    9.  If auto-callout was enabled in a pattern with a conditional group whose
557        condition was an assertion, PCRE could crash during matching, both with
558        pcre_exec() and pcre_dfa_exec().
560    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
561        used for matching.
563    11. Unicode property support in character classes was not working for
564        characters (bytes) greater than 127 when not in UTF-8 mode.
566    12. Added the -M command line option to pcretest.
568    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
570    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
572    16. Added comments and documentation about mis-use of no_arg in the C++
573        wrapper.
575    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
576        from Martin Jerabek that uses macro names for all relevant character and
577        string constants.
579    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
580        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
581        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
582        these, but not everybody uses configure.
584    19. A conditional group that had only one branch was not being correctly
585        recognized as an item that could match an empty string. This meant that an
586        enclosing group might also not be so recognized, causing infinite looping
587        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
588        with the subject "ab", where knowledge that the repeated group can match
589        nothing is needed in order to break the loop.
591    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
592        exec(), but without supplying a callout function, matching went wrong.
594    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
595        leak if the size of the offset vector was greater than 30. When the vector
596        is smaller, the saved offsets during recursion go onto a local stack
597        vector, but for larger vectors malloc() is used. It was failing to free
598        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
599        error, in fact).
601    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
602        heapframe that is used only when UTF-8 support is enabled. This caused no
603        problem, but was untidy.
605    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
606        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
607        included within another project.
609    24. Steven Van Ingelgem's patches to add more options to the CMake support,
610        slightly modified by me:
612          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
613              not building pcregrep.
615          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
616              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
618    25. Forward references, both numeric and by name, in patterns that made use of
619        duplicate group numbers, could behave incorrectly or give incorrect errors,
620        because when scanning forward to find the reference group, PCRE was not
621        taking into account the duplicate group numbers. A pattern such as
622        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
624    26. Changed a few more instances of "const unsigned char *" to USPTR, making
625        the feature of a custom pointer more persuasive (as requested by a user).
627    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
628        pcretest.c, inside #ifndefs, because it seems they are sometimes already
629        pre-defined.
631    28. Added support for (*UTF8) at the start of a pattern.
633    29. Arrange for flags added by the "release type" setting in CMake to be shown
634        in the configuration summary.
637    Version 7.8 05-Sep-08
638    ---------------------
640    1.  Replaced UCP searching code with optimized version as implemented for Ad
641        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
642        stage table and inline lookup instead of a function, giving speed ups of 2
643        to 5 times on some simple patterns that I tested. Permission was given to
644        distribute the MultiStage2.py script that generates the tables (it's not in
645        the tarball, but is in the Subversion repository).
647    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
648        scripts.
650    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
651        a group with a zero qualifier. The result of the study could be incorrect,
652        or the function might crash, depending on the pattern.
654    4.  Caseless matching was not working for non-ASCII characters in back
655        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
656        It now works when Unicode Property Support is available.
658    5.  In pcretest, an escape such as \x{de} in the data was always generating
659        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
660        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
661        truncation.
663    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
665    7.  Added two (int) casts to pcregrep when printing the difference of two
666        pointers, in case they are 64-bit values.
668    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
669        test 2 if it fails.
671    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
672        and a #define of that name to empty if it is not externally set. This is to
673        allow users of MSVC to set it if necessary.
675    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
676        the convenience functions in the pcre_get.c source file.
678    11. An option change at the start of a pattern that had top-level alternatives
679        could cause overwriting and/or a crash. This command provoked a crash in
680        some environments:
682          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
684        This potential security problem was recorded as CVE-2008-2371.
686    12. For a pattern where the match had to start at the beginning or immediately
687        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
688        pcre_dfa_exec() could read past the end of the passed subject if there was
689        no match. To help with detecting such bugs (e.g. with valgrind), I modified
690        pcretest so that it places the subject at the end of its malloc-ed buffer.
692    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
693        exec() might read past the end of the data buffer in UTF-8 mode.
695    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
696        the data contained the byte 0x85 as part of a UTF-8 character within its
697        first line. This applied both to normal and DFA matching.
699    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
700        /^[^d]*?$/8 failed to match "abc".
702    16. Added a missing copyright notice to pcrecpp_internal.h.
704    17. Make it more clear in the documentation that values returned from
705        pcre_exec() in ovector are byte offsets, not character counts.
707    18. Tidied a few places to stop certain compilers from issuing warnings.
709    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
710        supplied by Stefan Weber. I made a further small update for 7.8 because
711        there is a change of source arrangements: the pcre_searchfuncs.c module is
712        replaced by pcre_ucd.c.
715    Version 7.7 07-May-08
716    ---------------------
718    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
719        a string to a long long, pretend we don't even have a long long." This is
720        done by checking for the strtoq, strtoll, and _strtoi64 functions.
722    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
723        pre-7.6 versions, which defined a global no_arg variable instead of putting
724        it in the RE class. (See also #8 below.)
726    3.  Remove a line of dead code, identified by coverity and reported by Nuno
727        Lopes.
729    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
731        (1) The include/exclude patterns were being applied to the whole pathnames
732            of files, instead of just to the final components.
734        (2) If there was more than one level of directory, the subdirectories were
735            skipped unless they satisfied the include/exclude conditions. This is
736            inconsistent with GNU grep (and could even be seen as contrary to the
737            pcregrep specification - which I improved to make it absolutely clear).
738            The action now is always to scan all levels of directory, and just
739            apply the include/exclude patterns to regular files.
741    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
742        --exclude_dir in the tests to avoid scanning .svn directories.
744    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
745        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
746        doesn't support NULs in patterns.
748    7.  Added some missing "const"s to declarations of static tables in
749        pcre_compile.c and pcre_dfa_exec.c.
751    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
752        caused by fix #2  above. (Subsequently also a second patch to fix the
753        first patch. And a third patch - this was a messy problem.)
755    9.  Applied Craig's patch to remove the use of push_back().
757    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
758        matching function regexec().
760    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
761        which, however, unlike Perl's \g{...}, are subroutine calls, not back
762        references. PCRE supports relative numbers with this syntax (I don't think
763        Oniguruma does).
765    12. Previously, a group with a zero repeat such as (...){0} was completely
766        omitted from the compiled regex. However, this means that if the group
767        was called as a subroutine from elsewhere in the pattern, things went wrong
768        (an internal error was given). Such groups are now left in the compiled
769        pattern, with a new opcode that causes them to be skipped at execution
770        time.
772    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
773        to the way PCRE behaves:
775        (a) A lone ] character is dis-allowed (Perl treats it as data).
777        (b) A back reference to an unmatched subpattern matches an empty string
778            (Perl fails the current match path).
780        (c) A data ] in a character class must be notated as \] because if the
781            first data character in a class is ], it defines an empty class. (In
782            Perl it is not possible to have an empty class.) The empty class []
783            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
784            The negative empty class [^] matches any one character, independently
785            of the DOTALL setting.
787    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
788        non-existent subpattern following a character class starting with ']' and
789        containing () gave an internal compiling error instead of "reference to
790        non-existent subpattern". Fortunately, when the pattern did exist, the
791        compiled code was correct. (When scanning forwards to check for the
792        existencd of the subpattern, it was treating the data ']' as terminating
793        the class, so got the count wrong. When actually compiling, the reference
794        was subsequently set up correctly.)
796    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
797        it was being rejected as not supported by pcre_dfa_exec(), even though
798        other assertions are supported. I have made pcre_dfa_exec() support
799        (*FAIL).
801    16. The implementation of 13c above involved the invention of a new opcode,
802        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
803        cannot be changed at match time, I realized I could make a small
804        improvement to matching performance by compiling OP_ALLANY instead of
805        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
806        on the OP_ANY path.
808    17. Compiling pcretest on Windows with readline support failed without the
809        following two fixes: (1) Make the unistd.h include conditional on
810        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
812    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
813        ncurses library to be included for pcretest when ReadLine support is
814        requested, but also to allow for it to be overridden. This patch came from
815        Daniel Bergström.
817    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
818        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
819        any errors with the current Unicode tables. Thanks to Peter Kankowski for
820        spotting this.
823    Version 7.6 28-Jan-08
824    ---------------------
826    1.  A character class containing a very large number of characters with
827        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
828        overflow.
830    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
831        HAVE_LONG_LONG is not defined.
833    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
834        bring them up to date and include new features. This patch includes:
836        - Fixed PH's badly added libz and libbz2 support.
837        - Fixed a problem with static linking.
838        - Added pcredemo. [But later removed - see 7 below.]
839        - Fixed dftables problem and added an option.
840        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
841            HAVE_LONG_LONG.
842        - Added readline support for pcretest.
843        - Added an listing of the option settings after cmake has run.
845    4.  A user submitted a patch to Makefile that makes it easy to create
846        "pcre.dll" under mingw when using Configure/Make. I added stuff to
847        Makefile.am that cause it to include this special target, without
848        affecting anything else. Note that the same mingw target plus all
849        the other distribution libraries and programs are now supported
850        when configuring with CMake (see 6 below) instead of with
851        Configure/Make.
853    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
854        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
855        exported in the Windows port". It has not yet been confirmed that the patch
856        solves the problem, but it does no harm.
858    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
859        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
860        with CMake, and also correct the comment about stack recursion.
862    7.  Remove the automatic building of pcredemo from the ./configure system and
863        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
864        of a program that users should build themselves after PCRE is installed, so
865        building it automatically is not really right. What is more, it gave
866        trouble in some build environments.
868    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
871    Version 7.5 10-Jan-08
872    ---------------------
874    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
875        values in parens when parsing an RE using the C++ wrapper."
877    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
878        Characters greater than 255 were excluded from the class instead of being
879        included.
881    3.  The same bug as (2) above applied to negated POSIX classes such as
882        [:^space:].
884    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
885        defined or documented. It seems to have been a typo for PCRE_STATIC, so
886        I have changed it.
888    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
889        first named subpattern) and a construct such as (?&a) would reference the
890        first named subpattern whose name started with "a" (in other words, the
891        length check was missing). Both these problems are fixed. "Subpattern name
892        expected" is now given for (?&) (a zero-length name), and this patch also
893        makes it give the same error for \k'' (previously it complained that that
894        was a reference to a non-existent subpattern).
896    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
897        this is right because (?- can be followed by option settings as well as by
898        digits. I have, however, made the messages clearer.
900    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
901        than the number used in the conditional) now cause a compile-time error.
902        This is actually not compatible with Perl, which accepts such patterns, but
903        treats the conditional as always being FALSE (as PCRE used to), but it
904        seems to me that giving a diagnostic is better.
906    8.  Change "alphameric" to the more common word "alphanumeric" in comments
907        and messages.
909    9.  Fix two occurrences of "backslash" in comments that should have been
910        "backspace".
912    10. Remove two redundant lines of code that can never be obeyed (their function
913        was moved elsewhere).
915    11. The program that makes PCRE's Unicode character property table had a bug
916        which caused it to generate incorrect table entries for sequences of
917        characters that have the same character type, but are in different scripts.
918        It amalgamated them into a single range, with the script of the first of
919        them. In other words, some characters were in the wrong script. There were
920        thirteen such cases, affecting characters in the following ranges:
922          U+002b0 - U+002c1
923          U+0060c - U+0060d
924          U+0061e - U+00612
925          U+0064b - U+0065e
926          U+0074d - U+0076d
927          U+01800 - U+01805
928          U+01d00 - U+01d77
929          U+01d9b - U+01dbf
930          U+0200b - U+0200f
931          U+030fc - U+030fe
932          U+03260 - U+0327f
933          U+0fb46 - U+0fbb1
934          U+10450 - U+1049d
936    12. The -o option (show only the matching part of a line) for pcregrep was not
937        compatible with GNU grep in that, if there was more than one match in a
938        line, it showed only the first of them. It now behaves in the same way as
939        GNU grep.
941    13. If the -o and -v options were combined for pcregrep, it printed a blank
942        line for every non-matching line. GNU grep prints nothing, and pcregrep now
943        does the same. The return code can be used to tell if there were any
944        non-matching lines.
946    14. Added --file-offsets and --line-offsets to pcregrep.
948    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
949        infinitely looping recursion. The bug was that positive lookaheads were not
950        being skipped when checking for a possible empty match (negative lookaheads
951        and both kinds of lookbehind were skipped).
953    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
954        inclusion of <windows.h> to before rather than after the definition of
955        INVALID_FILE_ATTRIBUTES (patch from David Byron).
957    17. Specifying a possessive quantifier with a specific limit for a Unicode
958        character property caused pcre_compile() to compile bad code, which led at
959        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
960        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
961        caused the error; without that there was no problem.
963    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
965    19. Added --enable-pcretest-libreadline.
967    20. In pcrecpp.cc, the variable 'count' was incremented twice in
968        RE::GlobalReplace(). As a result, the number of replacements returned was
969        double what it should be. I removed one of the increments, but Craig sent a
970        later patch that removed the other one (the right fix) and added unit tests
971        that check the return values (which was not done before).
973    21. Several CMake things:
975        (1) Arranged that, when cmake is used on Unix, the libraries end up with
976            the names libpcre and libpcreposix, not just pcre and pcreposix.
978        (2) The above change means that pcretest and pcregrep are now correctly
979            linked with the newly-built libraries, not previously installed ones.
983    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
984        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
985        UTF-8 newline character). The key issue is that the pattern starts .*;
986        this means that the match must be either at the beginning, or after a
987        newline. The bug was in the code for advancing after a failed match and
988        checking that the new position followed a newline. It was not taking
989        account of UTF-8 characters correctly.
991    23. PCRE was behaving differently from Perl in the way it recognized POSIX
992        character classes. PCRE was not treating the sequence [:...:] as a
993        character class unless the ... were all letters. Perl, however, seems to
994        allow any characters between [: and :], though of course it rejects as
995        unknown any "names" that contain non-letters, because all the known class
996        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
997        for example, whereas PCRE did not - it did not recognize a POSIX character
998        class. This seemed a bit dangerous, so the code has been changed to be
999        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1000        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1001        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1002        Perl does, and where it didn't before.
1004    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1005        Windows environments %n is disabled by default.
1008    Version 7.4 21-Sep-07
1009    ---------------------
1011    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1012        means that a class such as [\s] counted as "explicit reference to CR or
1013        LF". That isn't really right - the whole point of the change was to try to
1014        help when there was an actual mention of one of the two characters. So now
1015        the change happens only if \r or \n (or a literal CR or LF) character is
1016        encountered.
1018    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1019        of both had grown to the point where there were only 3 bits left.
1020        Fortunately, there was spare space in the data structure, and so I have
1021        moved the internal flags into a new 16-bit field to free up more option
1022        bits.
1024    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1025        but did not set the internal JCHANGED flag - either of these is enough to
1026        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1027        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1028        start sets both bits.
1030    4.  Added options (at build time, compile time, exec time) to change \R from
1031        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1033    5.  doc/pcresyntax.html was missing from the distribution.
1035    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1036        compatibility, even though it is no longer used.
1038    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1039        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1040        windows.h file is present (where different names are used). [This was
1041        reversed later after testing - see 16 below.]
1043    8.  Changed all #include <config.h> to #include "config.h". There were also
1044        some further <pcre.h> cases that I changed to "pcre.h".
1046    9.  When pcregrep was used with the --colour option, it missed the line ending
1047        sequence off the lines that it output.
1049    10. It was pointed out to me that arrays of string pointers cause lots of
1050        relocations when a shared library is dynamically loaded. A technique of
1051        using a single long string with a table of offsets can drastically reduce
1052        these. I have refactored PCRE in four places to do this. The result is
1053        dramatic:
1055          Originally:                          290
1056          After changing UCP table:            187
1057          After changing error message table:   43
1058          After changing table of "verbs"       36
1059          After changing table of Posix names   22
1061        Thanks to the folks working on Gregex for glib for this insight.
1063    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1064        unicode-properties was also set.
1066    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1068    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1069        checked only for CRLF.
1071    14. Added casts to pcretest.c to avoid compiler warnings.
1073    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1075    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1076        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1077        entirely. This removes changes made in 7 above.
1079    17. The CMake files have been updated, and there is now more information about
1080        building with CMake in the NON-UNIX-USE document.
1083    Version 7.3 28-Aug-07
1084    ---------------------
1086     1. In the rejigging of the build system that eventually resulted in 7.1, the
1087        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
1088        brackets there is not right, since it causes compilers to look for an
1089        installed pcre.h, not the version that is in the source that is being
1090        compiled (which of course may be different). I have changed it back to:
1092          #include "pcre.h"
1094        I have a vague recollection that the change was concerned with compiling in
1095        different directories, but in the new build system, that is taken care of
1096        by the VPATH setting the Makefile.
1098     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
1099        when the subject happened to end in the byte 0x85 (e.g. if the last
1100        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
1101        characters but of course it shouldn't be taken as a newline when it is part
1102        of another character. The bug was that, for an unlimited repeat of . in
1103        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
1104        characters when looking for a newline.
1106     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
1108     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
1109        in debug output.
1111     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
1112        long printing in the pcrecpp unittest when running under MinGW.
1114     6. ESC_K was left out of the EBCDIC table.
1116     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
1117        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
1118        limit also applies to "virtual nesting" when a pattern is recursive, and in
1119        this case 1000 isn't so big. I have been able to remove this limit at the
1120        expense of backing off one optimization in certain circumstances. Normally,
1121        when pcre_exec() would call its internal match() function recursively and
1122        immediately return the result unconditionally, it uses a "tail recursion"
1123        feature to save stack. However, when a subpattern that can match an empty
1124        string has an unlimited repetition quantifier, it no longer makes this
1125        optimization. That gives it a stack frame in which to save the data for
1126        checking that an empty string has been matched. Previously this was taken
1127        from the 1000-entry workspace that had been reserved. So now there is no
1128        explicit limit, but more stack is used.
1130     8. Applied Daniel's patches to solve problems with the import/export magic
1131        syntax that is required for Windows, and which was going wrong for the
1132        pcreposix and pcrecpp parts of the library. These were overlooked when this
1133        problem was solved for the main library.
1135     9. There were some crude static tests to avoid integer overflow when computing
1136        the size of patterns that contain repeated groups with explicit upper
1137        limits. As the maximum quantifier is 65535, the maximum group length was
1138        set at 30,000 so that the product of these two numbers did not overflow a
1139        32-bit integer. However, it turns out that people want to use groups that
1140        are longer than 30,000 bytes (though not repeat them that many times).
1141        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
1142        made it possible to implement the integer overflow checks in a much more
1143        dynamic way, which I have now done. The artificial limitation on group
1144        length has been removed - we now have only the limit on the total length of
1145        the compiled pattern, which depends on the LINK_SIZE setting.
1147    10. Fixed a bug in the documentation for get/copy named substring when
1148        duplicate names are permitted. If none of the named substrings are set, the
1149        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1150        empty string.
1152    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1153        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1154        because the ] is interpreted as the first data character and the
1155        terminating ] is not found. PCRE has been made compatible with Perl in this
1156        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1157        cause memory overwriting.
1159    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1160        string has been matched (to stop an infinite loop). It was not recognizing
1161        a conditional subpattern that could match an empty string if that
1162        subpattern was within another subpattern. For example, it looped when
1163        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1164        condition was not nested. This bug has been fixed.
1166    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1167        past the start of the subject in the presence of bytes with the top bit
1168        set, for example "\x8aBCD".
1170    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1171        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1173    14. Optimized (?!) to (*FAIL).
1175    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1176        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1177        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1178        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1179        does: it's just the validity check that is more restrictive.
1181    16. Inserted checks for integer overflows during escape sequence (backslash)
1182        processing, and also fixed erroneous offset values for syntax errors during
1183        backslash processing.
1185    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1186        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1188    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1189        caused an overrun.
1191    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1192        something other than just ASCII characters) inside a group that had an
1193        unlimited repeat caused a loop at compile time (while checking to see
1194        whether the group could match an empty string).
1196    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1197        [\P{Any}] did so. (Error in the code for printing property names.)
1199    21. An orphan \E inside a character class could cause a crash.
1201    22. A repeated capturing bracket such as (A)? could cause a wild memory
1202        reference during compilation.
1204    23. There are several functions in pcre_compile() that scan along a compiled
1205        expression for various reasons (e.g. to see if it's fixed length for look
1206        behind). There were bugs in these functions when a repeated \p or \P was
1207        present in the pattern. These operators have additional parameters compared
1208        with \d, etc, and these were not being taken into account when moving along
1209        the compiled data. Specifically:
1211        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1212            length.
1214        (b) An item such as \pL+ within a repeated group could cause crashes or
1215            loops.
1217        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1218            "reference to non-existent subpattern" error.
1220        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1222    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1223        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1225    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1227    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1228        character were causing crashes (broken optimization).
1230    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1231        \p or \P) caused a compile-time loop.
1233    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1234        break. For example, the unstudied pattern [\r\n]A does not match the string
1235        "\r\nA" because change 7.0/46 below moves the current point on by two
1236        characters after failing to match at the start. However, the pattern \nA
1237        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1238        the same is true. There doesn't seem any very clean way out of this, but
1239        what I have chosen to do makes the common cases work: PCRE now takes note
1240        of whether there can be an explicit match for \r or \n anywhere in the
1241        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1242        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1243        pattern has explicit CR or LF references.
1245    29. Added (*CR) etc for changing newline setting at start of pattern.
1248    Version 7.2 19-Jun-07
1249    ---------------------
1251     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1252        which is apparently normally available under Windows.
1254     2. Re-jig the pcregrep tests with different newline settings in an attempt
1255        to make them independent of the local environment's newline setting.
1257     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1259     4. Some of the "internals" tests were previously cut out when the link size
1260        was not 2, because the output contained actual offsets. The recent new
1261        "Z" feature of pcretest means that these can be cut out, making the tests
1262        usable with all link sizes.
1264     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1265        stack recursion. This gives a massive performance boost under BSD, but just
1266        a small improvement under Linux. However, it saves one field in the frame
1267        in all cases.
1269     6. Added more features from the forthcoming Perl 5.10:
1271        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1272            recursion call. It refers to the nth most recently opened parentheses.
1274        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1275            to be opened parentheses.
1277        (c) Conditions that refer to capturing parentheses can be specified
1278            relatively, for example, (?(-2)... or (?(+3)...
1280        (d) \K resets the start of the current match so that everything before
1281            is not part of it.
1283        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1285        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1286            reference syntax.
1288        (g) (?| introduces a group in which the numbering of parentheses in each
1289            alternative starts with the same number.
1291        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1293     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1296     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1297        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1298        for detecting groups that can match an empty string.
1300     9. A pattern with a very large number of alternatives (more than several
1301        hundred) was running out of internal workspace during the pre-compile
1302        phase, where pcre_compile() figures out how much memory will be needed. A
1303        bit of new cunning has reduced the workspace needed for groups with
1304        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1305        workspace instead of running out of the 4096 that are available.
1307    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1309    11. Applied patch from Google to remove an optimization that didn't quite work.
1310        The report of the bug said:
1312          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1313          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1314          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1316    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1317        it matched the wrong number of bytes.
1320    Version 7.1 24-Apr-07
1321  ---------------------  ---------------------
1323   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 26  Version 7.1 12-Mar-07 Line 1342  Version 7.1 12-Mar-07
1342      .br or .in.      .br or .in.
1344   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
1345      arranged for config.h to be included in the distribution, with the name      arranged for config.h to be included in the distribution, with the name
1346      config.h.generic, for the benefit of those who have to compile without      config.h.generic, for the benefit of those who have to compile without
1347      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
1349   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
1350      Weber: (1) pcre_internal.h was missing some function renames; (2) updated      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
1351      makevp.bat for the current PCRE, using the additional files !compile.txt,      makevp.bat for the current PCRE, using the additional files
1352      !linklib.txt, and pcregexp.pas.      makevp_c.txt, makevp_l.txt, and pcregexp.pas.
1354   6. A Windows user reported a minor discrepancy with test 2, which turned out   6. A Windows user reported a minor discrepancy with test 2, which turned out
1355      to be caused by a trailing space on an input line that had got lost in his      to be caused by a trailing space on an input line that had got lost in his
# Line 63  Version 7.1 12-Mar-07 Line 1379  Version 7.1 12-Mar-07
1379  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
1381      (a) It was defining its arguments as char * instead of void *.      (a) It was defining its arguments as char * instead of void *.
1383      (b) It was assuming that all moves were upwards in memory; this was true      (b) It was assuming that all moves were upwards in memory; this was true
1384          a long time ago when I wrote it, but is no longer the case.          a long time ago when I wrote it, but is no longer the case.
1386      The emulated memove() is provided for those environments that have neither      The emulated memove() is provided for those environments that have neither
1387      memmove() nor bcopy(). I didn't think anyone used it these days, but that      memmove() nor bcopy(). I didn't think anyone used it these days, but that
1388      is clearly not the case, as these two bugs were recently reported.      is clearly not the case, as these two bugs were recently reported.
1390  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
1391      and Detrail to create the HTML documentation, the .txt form of the man      and Detrail to create the HTML documentation, the .txt form of the man
1392      pages, and it removes trailing spaces from listed files. It also creates      pages, and it removes trailing spaces from listed files. It also creates
1393      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
1394      case, it wraps all the #defines with #ifndefs. This script should be run      case, it wraps all the #defines with #ifndefs. This script should be run
1395      before "make dist".      before "make dist".
1397  12. Fixed two fairly obscure bugs concerned with quantified caseless matching  12. Fixed two fairly obscure bugs concerned with quantified caseless matching
1398      with Unicode property support.      with Unicode property support.
1400      (a) For a maximizing quantifier, if the two different cases of the      (a) For a maximizing quantifier, if the two different cases of the
1401          character were of different lengths in their UTF-8 codings (there are          character were of different lengths in their UTF-8 codings (there are
1402          some cases like this - I found 11), and the matching function had to          some cases like this - I found 11), and the matching function had to
1403          back up over a mixture of the two cases, it incorrectly assumed they          back up over a mixture of the two cases, it incorrectly assumed they
1404          were both the same length.          were both the same length.
1406      (b) When PCRE was configured to use the heap rather than the stack for      (b) When PCRE was configured to use the heap rather than the stack for
1407          recursion during matching, it was not correctly preserving the data for          recursion during matching, it was not correctly preserving the data for
1408          the other case of a UTF-8 character when checking ahead for a match          the other case of a UTF-8 character when checking ahead for a match
1409          while processing a minimizing repeat. If the check also involved          while processing a minimizing repeat. If the check also involved
1410          matching a wide character, but failed, corruption could cause an          matching a wide character, but failed, corruption could cause an
1411          erroneous result when trying to check for a repeat of the original          erroneous result when trying to check for a repeat of the original
1412          character.          character.
1414  13. Some tidying changes to the testing mechanism:  13. Some tidying changes to the testing mechanism:
1416      (a) The RunTest script now detects the internal link size and whether there      (a) The RunTest script now detects the internal link size and whether there
1417          is UTF-8 and UCP support by running ./pcretest -C instead of relying on          is UTF-8 and UCP support by running ./pcretest -C instead of relying on
1418          values substituted by "configure". (The RunGrepTest script already did          values substituted by "configure". (The RunGrepTest script already did
1419          this for UTF-8.) The configure.ac script no longer substitutes the          this for UTF-8.) The configure.ac script no longer substitutes the
1420          relevant variables.          relevant variables.
1422      (b) The debugging options /B and /D in pcretest show the compiled bytecode      (b) The debugging options /B and /D in pcretest show the compiled bytecode
1423          with length and offset values. This means that the output is different          with length and offset values. This means that the output is different
1424          for different internal link sizes. Test 2 is skipped for link sizes          for different internal link sizes. Test 2 is skipped for link sizes
1425          other than 2 because of this, bypassing the problem. Unfortunately,          other than 2 because of this, bypassing the problem. Unfortunately,
1426          there was also a test in test 3 (the locale tests) that used /B and          there was also a test in test 3 (the locale tests) that used /B and
1427          failed for link sizes other than 2. Rather than cut the whole test out,          failed for link sizes other than 2. Rather than cut the whole test out,
1428          I have added a new /Z option to pcretest that replaces the length and          I have added a new /Z option to pcretest that replaces the length and
1429          offset values with spaces. This is now used to make test 3 independent          offset values with spaces. This is now used to make test 3 independent
1430          of link size. (Test 2 will be tidied up later.)          of link size. (Test 2 will be tidied up later.)
1432  14. If erroroffset was passed as NULL to pcre_compile, it provoked a  14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1433      segmentation fault instead of returning the appropriate error message.      segmentation fault instead of returning the appropriate error message.
1435    15. In multiline mode when the newline sequence was set to "any", the pattern
1436        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1437        This doesn't seem right; it now treats the CRLF combination as the line
1438        ending, and so does not match in that case. It's only a pattern such as ^$
1439        that would hit this one: something like ^ABC$ would have failed after \r
1440        and then tried again after \r\n.
1442    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1443        in an attempt to make files that differ only in their line terminators
1444        compare equal. This works on Linux.
1446    17. Under certain error circumstances pcregrep might try to free random memory
1447        as it exited. This is now fixed, thanks to valgrind.
1449    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1450        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1451        was because its rules for how to advance for /g after matching an empty
1452        string at the end of a line did not allow for this case. They now check for
1453        it specially.
1455    20. pcretest is supposed to handle patterns and data of any length, by
1456        extending its buffers when necessary. It was getting this wrong when the
1457        buffer for a data line had to be extended.
1459    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1460        CRLF as a newline sequence.
1462    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1463        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1464        I have nevertheless tidied it up.
1466    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1468    24. Added a man page for pcre-config.
1471  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1472  ---------------------  ---------------------

Removed from v.122  
changed lines
  Added in v.561

  ViewVC Help
Powered by ViewVC 1.1.5