ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 353 by ph10, Mon Jul 7 15:44:24 2008 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 8.0 02 Jul-08  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  1.  Replaced UCP searching code with optimized version as implemented for Ad
# Line 13  Version 8.0 02 Jul-08 Line 646  Version 8.0 02 Jul-08
647  2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more  2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
648      scripts.      scripts.
650  3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained  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,      a group with a zero qualifier. The result of the study could be incorrect,
652      or the function might crash, depending on the pattern.      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  Version 7.7 07-May-08

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

  ViewVC Help
Powered by ViewVC 1.1.5