ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 389 by ph10, Sun Mar 15 18:24:05 2009 UTC revision 565 by ph10, Sun Oct 31 18:18:48 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.9 xx-xxx-09  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.
62    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
64    11. When the -o option was used, pcregrep was setting a return code of 1, even
65        when matches were found, and --line-buffered was not being honoured.
67    12. Added an optional parentheses number to the -o and --only-matching options
68        of pcregrep.
71    Version 8.10 25-Jun-2010
72    ------------------------
74    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
75        THEN.
77    2.  (*ACCEPT) was not working when inside an atomic group.
79    3.  Inside a character class, \B is treated as a literal by default, but
80        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
81        causes the error). The code is unchanged, but I tidied the documentation.
83    4.  Inside a character class, PCRE always treated \R and \X as literals,
84        whereas Perl faults them if its -w option is set. I have changed PCRE so
85        that it faults them when PCRE_EXTRA is set.
87    5.  Added support for \N, which always matches any character other than
88        newline. (It is the same as "." when PCRE_DOTALL is not set.)
90    6.  When compiling pcregrep with newer versions of gcc which may have
91        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
92        declared with attribute warn_unused_result" were given. Just casting the
93        result to (void) does not stop the warnings; a more elaborate fudge is
94        needed. I've used a macro to implement this.
96    7.  Minor change to pcretest.c to avoid a compiler warning.
98    8.  Added four artifical Unicode properties to help with an option to make
99        \s etc use properties (see next item). The new properties are: Xan
100        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
102    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
103        use Unicode properties. (*UCP) at the start of a pattern can be used to set
104        this option. Modified pcretest to add /W to test this facility. Added
105        REG_UCP to make it available via the POSIX interface.
107    10. Added --line-buffered to pcregrep.
109    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
110        studied, and the match started with a letter with a code point greater than
111        127 whose first byte was different to the first byte of the other case of
112        the letter, the other case of this starting letter was not recognized
113        (#976).
115    12. If a pattern that was studied started with a repeated Unicode property
116        test, for example, \p{Nd}+, there was the theoretical possibility of
117        setting up an incorrect bitmap of starting bytes, but fortunately it could
118        not have actually happened in practice until change 8 above was made (it
119        added property types that matched character-matching opcodes).
121    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
122        possible starting bytes for non-anchored patterns.
124    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
125        \R, and also a number of cases that involve Unicode properties, both
126        explicit and implicit when PCRE_UCP is set.
128    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
129        input, it could crash or give wrong results if characters with values
130        greater than 0xc0 were present in the subject string. (Detail: it assumed
131        UTF-8 input when processing these items.)
133    16. Added a lot of (int) casts to avoid compiler warnings in systems where
134        size_t is 64-bit (#991).
136    17. Added a check for running out of memory when PCRE is compiled with
137        --disable-stack-for-recursion (#990).
139    18. If the last data line in a file for pcretest does not have a newline on
140        the end, a newline was missing in the output.
142    19. The default pcre_chartables.c file recognizes only ASCII characters (values
143        less than 128) in its various bitmaps. However, there is a facility for
144        generating tables according to the current locale when PCRE is compiled. It
145        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
146        characters, are recognized by isspace() and therefore were getting set in
147        these tables, and indeed these tables seem to approximate to ISO 8859. This
148        caused a problem in UTF-8 mode when pcre_study() was used to create a list
149        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
150        which of course cannot start UTF-8 characters. I have changed the code so
151        that only real ASCII characters (less than 128) and the correct starting
152        bytes for UTF-8 encodings are set for characters greater than 127 when in
153        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
154        altogether.)
156    20. Added the /T option to pcretest so as to be able to run tests with non-
157        standard character tables, thus making it possible to include the tests
158        used for 19 above in the standard set of tests.
160    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
161        reference to a subpattern the other side of a comment that contains an
162        opening parenthesis caused either an internal compiling error, or a
163        reference to the wrong subpattern.
166    Version 8.02 19-Mar-2010
167    ------------------------
169    1.  The Unicode data tables have been updated to Unicode 5.2.0.
171    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
172        configured.
174    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
175        original author of that file, following a query about its status.
177    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
178        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
180    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
181        quantifier applied to a forward-referencing subroutine call, could compile
182        incorrect code or give the error "internal error: previously-checked
183        referenced subpattern not found".
185    6.  Both MS Visual Studio and Symbian OS have problems with initializing
186        variables to point to external functions. For these systems, therefore,
187        pcre_malloc etc. are now initialized to local functions that call the
188        relevant global functions.
190    7.  There were two entries missing in the vectors called coptable and poptable
191        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
192        I've fixed the data, and added a kludgy way of testing at compile time that
193        the lengths are correct (equal to the number of opcodes).
195    8.  Following on from 7, I added a similar kludge to check the length of the
196        eint vector in pcreposix.c.
198    9.  Error texts for pcre_compile() are held as one long string to avoid too
199        much relocation at load time. To find a text, the string is searched,
200        counting zeros. There was no check for running off the end of the string,
201        which could happen if a new error number was added without updating the
202        string.
204    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
206    11. \K was not working if it appeared in an atomic group or in a group that
207        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
208        \K is "not well defined" if used in an assertion. PCRE now accepts it if
209        the assertion is positive, but not if it is negative.
211    12. Change 11 fortuitously reduced the size of the stack frame used in the
212        "match()" function of pcre_exec.c by one pointer. Forthcoming
213        implementation of support for (*MARK) will need an extra pointer on the
214        stack; I have reserved it now, so that the stack frame size does not
215        decrease.
217    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
218        item in branch that calls a recursion is a subroutine call - as in the
219        second branch in the above example - was incorrectly given the compile-
220        time error "recursive call could loop indefinitely" because pcre_compile()
221        was not correctly checking the subroutine for matching a non-empty string.
223    14. The checks for overrunning compiling workspace could trigger after an
224        overrun had occurred. This is a "should never occur" error, but it can be
225        triggered by pathological patterns such as hundreds of nested parentheses.
226        The checks now trigger 100 bytes before the end of the workspace.
228    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
231    Version 8.01 19-Jan-2010
232    ------------------------
234    1.  If a pattern contained a conditional subpattern with only one branch (in
235        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
236        computed the wrong minimum data length (which is of course zero for such
237        subpatterns). This could cause incorrect "no match" results.
239    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
240        the pattern is reset in the first branch, pcre_compile() failed with
241        "internal error: code overflow at offset...". This happened only when
242        the reset was to the original external option setting. (An optimization
243        abstracts leading options settings into an external setting, which was the
244        cause of this.)
246    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
247        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
248        assertion pattern did not match (meaning that the assertion was true), it
249        was incorrectly treated as false if the SKIP had been reached during the
250        matching. This also applied to assertions used as conditions.
252    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
253        assertion subpattern, including such a pattern used as a condition,
254        unpredictable results occurred, instead of the error return
257    5.  The C++ GlobalReplace function was not working like Perl for the special
258        situation when an empty string is matched. It now does the fancy magic
259        stuff that is necessary.
261    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
262        removed. (These were left over from very, very early versions of PCRE.)
264    7.  Some cosmetic changes to the code to make life easier when compiling it
265        as part of something else:
267        (a) Change DEBUG to PCRE_DEBUG.
269        (b) In pcre_compile(), rename the member of the "branch_chain" structure
270            called "current" as "current_branch", to prevent a collision with the
271            Linux macro when compiled as a kernel module.
273        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
274            prevent a collision with the Linux macro when compiled as a kernel
275            module.
277    8.  In pcre_compile() there are some checks for integer overflows that used to
278        cast potentially large values to (double). This has been changed to that
279        when building, a check for int64_t is made, and if it is found, it is used
280        instead, thus avoiding the use of floating point arithmetic. (There is no
281        other use of FP in PCRE.) If int64_t is not found, the fallback is to
282        double.
284    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
285        2005 (difference between two addresses compared to an unsigned value).
287    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
288        custom one, because of the following reported problem in Windows:
290          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
291              under Win32.
292          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
293              therefore missing the function definition.
294          - The compiler thus generates a "C" signature for the test function.
295          - The linker fails to find the "C" function.
296          - PCRE fails to configure if asked to do so against libbz2.
298    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
299        messages were output:
301          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
302          rerunning libtoolize, to keep the correct libtool macros in-tree.
303          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
305        I have done both of these things.
307    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
308        most of the time, it *can* run out if it is given a pattern that contains a
309        runaway infinite recursion. I updated the discussion in the pcrestack man
310        page.
312    13. Now that we have gone to the x.xx style of version numbers, the minor
313        version may start with zero. Using 08 or 09 is a bad idea because users
314        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
315        interpreted as invalid octal numbers. I've updated the previous comment in
316        configure.ac, and also added a check that gives an error if 08 or 09 are
317        used.
319    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
320        causing partial matching to fail when the end of the subject matched \W
321        in a UTF-8 pattern where \W was quantified with a minimum of 3.
323    15. There were some discrepancies between the declarations in pcre_internal.h
324        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
325        their definitions. The declarations used "const uschar *" and the
326        definitions used USPTR. Even though USPTR is normally defined as "const
327        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
328        reported that: "This difference in casting confuses some C++ compilers, for
329        example, SunCC recognizes above declarations as different functions and
330        generates broken code for hbpcre." I have changed the declarations to use
331        USPTR.
333    16. GNU libtool is named differently on some systems. The autogen.sh script now
334        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
335        (FreeBSD).
337    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
338        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
339        comment: "Figure out how to create a longlong from a string: strtoll and
340        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
341        instance, but it only takes 2 args instead of 3!"
343    18. A subtle bug concerned with back references has been fixed by a change of
344        specification, with a corresponding code fix. A pattern such as
345        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
346        refers, was giving matches when it shouldn't. For example, xa=xaaa would
347        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
348        same bug. Such groups have to be quantified to be useful, or contained
349        inside another quantified group. (If there's no repetition, the reference
350        can never match.) The problem arises because, having left the group and
351        moved on to the rest of the pattern, a later failure that backtracks into
352        the group uses the captured value from the final iteration of the group
353        rather than the correct earlier one. I have fixed this in PCRE by forcing
354        any group that contains a reference to itself to be an atomic group; that
355        is, there cannot be any backtracking into it once it has completed. This is
356        similar to recursive and subroutine calls.
359    Version 8.00 19-Oct-09
360    ----------------------
362    1.  The table for translating pcre_compile() error codes into POSIX error codes
363        was out-of-date, and there was no check on the pcre_compile() error code
364        being within the table. This could lead to an OK return being given in
365        error.
367    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
368        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
369        in a Windows environment.
371    3.  The pcregrep --count option prints the count for each file even when it is
372        zero, as does GNU grep. However, pcregrep was also printing all files when
373        --files-with-matches was added. Now, when both options are given, it prints
374        counts only for those files that have at least one match. (GNU grep just
375        prints the file name in this circumstance, but including the count seems
376        more useful - otherwise, why use --count?) Also ensured that the
377        combination -clh just lists non-zero counts, with no names.
379    4.  The long form of the pcregrep -F option was incorrectly implemented as
380        --fixed_strings instead of --fixed-strings. This is an incompatible change,
381        but it seems right to fix it, and I didn't think it was worth preserving
382        the old behaviour.
384    5.  The command line items --regex=pattern and --regexp=pattern were not
385        recognized by pcregrep, which required --regex pattern or --regexp pattern
386        (with a space rather than an '='). The man page documented the '=' forms,
387        which are compatible with GNU grep; these now work.
389    6.  No libpcreposix.pc file was created for pkg-config; there was just
390        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
392    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
393        when UCP support is not needed, by modifying the Python script that
394        generates it from Unicode data files. This should not matter if the module
395        is correctly used as a library, but I received one complaint about 50K of
396        unwanted data. My guess is that the person linked everything into his
397        program rather than using a library. Anyway, it does no harm.
399    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
400        was a minimum greater than 1 for a wide character in a possessive
401        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
402        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
403        character. Chaos in the form of incorrect output or a compiling loop could
404        result.
406    9.  The restrictions on what a pattern can contain when partial matching is
407        requested for pcre_exec() have been removed. All patterns can now be
408        partially matched by this function. In addition, if there are at least two
409        slots in the offset vector, the offset of the earliest inspected character
410        for the match and the offset of the end of the subject are set in them when
411        PCRE_ERROR_PARTIAL is returned.
413    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
414        synonymous with PCRE_PARTIAL, for backwards compatibility, and
415        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
416        and may be more useful for multi-segment matching.
418    11. Partial matching with pcre_exec() is now more intuitive. A partial match
419        used to be given if ever the end of the subject was reached; now it is
420        given only if matching could not proceed because another character was
421        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
422        string "Z", which now yields "no match" instead of "partial match". In the
423        case of pcre_dfa_exec(), "no match" is given if every matching path for the
424        final character ended with (*FAIL).
426    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
427        if the pattern had a "must contain" character that was already found in the
428        earlier partial match, unless partial matching was again requested. For
429        example, with the pattern /dog.(body)?/, the "must contain" character is
430        "g". If the first part-match was for the string "dog", restarting with
431        "sbody" failed. This bug has been fixed.
433    13. The string returned by pcre_dfa_exec() after a partial match has been
434        changed so that it starts at the first inspected character rather than the
435        first character of the match. This makes a difference only if the pattern
436        starts with a lookbehind assertion or \b or \B (\K is not supported by
437        pcre_dfa_exec()). It's an incompatible change, but it makes the two
438        matching functions compatible, and I think it's the right thing to do.
440    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
441        so that the demonstration program is easily available in environments where
442        PCRE has not been installed from source.
444    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
445        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
446        library.
448    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
449        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
450        is not the first non-POSIX option to be added. Clearly some people find
451        these options useful.
453    17. If a caller to the POSIX matching function regexec() passes a non-zero
454        value for nmatch with a NULL value for pmatch, the value of
455        nmatch is forced to zero.
457    18. RunGrepTest did not have a test for the availability of the -u option of
458        the diff command, as RunTest does. It now checks in the same way as
459        RunTest, and also checks for the -b option.
461    19. If an odd number of negated classes containing just a single character
462        interposed, within parentheses, between a forward reference to a named
463        subpattern and the definition of the subpattern, compilation crashed with
464        an internal error, complaining that it could not find the referenced
465        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
466        [The bug was that it was starting one character too far in when skipping
467        over the character class, thus treating the ] as data rather than
468        terminating the class. This meant it could skip too much.]
470    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
471        /g option in pcretest when the pattern contains \K, which makes it possible
472        to have an empty string match not at the start, even when the pattern is
473        anchored. Updated pcretest and pcredemo to use this option.
475    21. If the maximum number of capturing subpatterns in a recursion was greater
476        than the maximum at the outer level, the higher number was returned, but
477        with unset values at the outer level. The correct (outer level) value is
478        now given.
480    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
481        PCRE did not set those parentheses (unlike Perl). I have now found a way to
482        make it do so. The string so far is captured, making this feature
483        compatible with Perl.
485    23. The tests have been re-organized, adding tests 11 and 12, to make it
486        possible to check the Perl 5.10 features against Perl 5.10.
488    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
489        pattern matches a fixed length string. PCRE did not allow this; now it
490        does. Neither allows recursion.
492    25. I finally figured out how to implement a request to provide the minimum
493        length of subject string that was needed in order to match a given pattern.
494        (It was back references and recursion that I had previously got hung up
495        on.) This code has now been added to pcre_study(); it finds a lower bound
496        to the length of subject needed. It is not necessarily the greatest lower
497        bound, but using it to avoid searching strings that are too short does give
498        some useful speed-ups. The value is available to calling programs via
499        pcre_fullinfo().
501    26. While implementing 25, I discovered to my embarrassment that pcretest had
502        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
503        study optimizations had never been tested with that matching function.
504        Oops. What is worse, even when it was passed study data, there was a bug in
505        pcre_dfa_exec() that meant it never actually used it. Double oops. There
506        were also very few tests of studied patterns with pcre_dfa_exec().
508    27. If (?| is used to create subpatterns with duplicate numbers, they are now
509        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
510        on the other side of the coin, they are no longer allowed to have different
511        names, because these cannot be distinguished in PCRE, and this has caused
512        confusion. (This is a difference from Perl.)
514    28. When duplicate subpattern names are present (necessarily with different
515        numbers, as required by 27 above), and a test is made by name in a
516        conditional pattern, either for a subpattern having been matched, or for
517        recursion in such a pattern, all the associated numbered subpatterns are
518        tested, and the overall condition is true if the condition is true for any
519        one of them. This is the way Perl works, and is also more like the way
520        testing by number works.
523    Version 7.9 11-Apr-09
524  ---------------------  ---------------------
526  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
527      (pcretest), all targets were linked against these libraries. This included      (pcretest), all targets were linked against these libraries. This included
528      libpcre, libpcreposix, and libpcrecpp, even though they do not use these      libpcre, libpcreposix, and libpcrecpp, even though they do not use these
529      libraries. This caused unwanted dependencies to be created. This problem      libraries. This caused unwanted dependencies to be created. This problem
530      has been fixed, and now only pcregrep is linked with bzlib/zlib and only      has been fixed, and now only pcregrep is linked with bzlib/zlib and only
531      pcretest is linked with readline.      pcretest is linked with readline.
533  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the  2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
534      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been      "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
535      moved outside it again, because FALSE and TRUE are already defined in AIX,      moved outside it again, because FALSE and TRUE are already defined in AIX,
536      but BOOL is not.      but BOOL is not.
538  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
539      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
541  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
542      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
543      lines. This is not true; no spaces are inserted. I have also clarified the      lines. This is not true; no spaces are inserted. I have also clarified the
544      wording for the --colour (or --color) option.      wording for the --colour (or --color) option.
546  5.  In pcregrep, when --colour was used with -o, the list of matching strings  5.  In pcregrep, when --colour was used with -o, the list of matching strings
547      was not coloured; this is different to GNU grep, so I have changed it to be      was not coloured; this is different to GNU grep, so I have changed it to be
548      the same.      the same.
550  6.  When --colo(u)r was used in pcregrep, only the first matching substring in  6.  When --colo(u)r was used in pcregrep, only the first matching substring in
551      each matching line was coloured. Now it goes on to look for further matches      each matching line was coloured. Now it goes on to look for further matches
552      of any of the test patterns, which is the same behaviour as GNU grep.      of any of the test patterns, which is the same behaviour as GNU grep.
554  7.  A pattern that could match an empty string could cause pcregrep to loop; it  7.  A pattern that could match an empty string could cause pcregrep to loop; it
555      doesn't make sense to accept an empty string match in pcregrep, so I have      doesn't make sense to accept an empty string match in pcregrep, so I have
556      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this      locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
557      seems to be how GNU grep behaves.      seems to be how GNU grep behaves.
559  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at  8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
560      start or after a newline", because the conditional assertion was not being      start or after a newline", because the conditional assertion was not being
561      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
562      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
564  9.  If auto-callout was enabled in a pattern with a conditional group, PCRE  9.  If auto-callout was enabled in a pattern with a conditional group whose
565      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
566        pcre_exec() and pcre_dfa_exec().
567  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  
568      used for matching.  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
569        used for matching.
570  11. Unicode property support in character classes was not working for  
571    11. Unicode property support in character classes was not working for
572      characters (bytes) greater than 127 when not in UTF-8 mode.      characters (bytes) greater than 127 when not in UTF-8 mode.
574  12. Added the -M command line option to pcretest.  12. Added the -M command line option to pcretest.
576  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.  14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
578  15. Added the PCRE_NO_START_OPTIMIZE match-time option.  15. Added the PCRE_NO_START_OPTIMIZE match-time option.
580    16. Added comments and documentation about mis-use of no_arg in the C++
581        wrapper.
583    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
584        from Martin Jerabek that uses macro names for all relevant character and
585        string constants.
587    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
588        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
589        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
590        these, but not everybody uses configure.
592    19. A conditional group that had only one branch was not being correctly
593        recognized as an item that could match an empty string. This meant that an
594        enclosing group might also not be so recognized, causing infinite looping
595        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
596        with the subject "ab", where knowledge that the repeated group can match
597        nothing is needed in order to break the loop.
599    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
600        exec(), but without supplying a callout function, matching went wrong.
602    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
603        leak if the size of the offset vector was greater than 30. When the vector
604        is smaller, the saved offsets during recursion go onto a local stack
605        vector, but for larger vectors malloc() is used. It was failing to free
606        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
607        error, in fact).
609    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
610        heapframe that is used only when UTF-8 support is enabled. This caused no
611        problem, but was untidy.
613    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
614        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
615        included within another project.
617    24. Steven Van Ingelgem's patches to add more options to the CMake support,
618        slightly modified by me:
620          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
621              not building pcregrep.
623          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
624              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
626    25. Forward references, both numeric and by name, in patterns that made use of
627        duplicate group numbers, could behave incorrectly or give incorrect errors,
628        because when scanning forward to find the reference group, PCRE was not
629        taking into account the duplicate group numbers. A pattern such as
630        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
632    26. Changed a few more instances of "const unsigned char *" to USPTR, making
633        the feature of a custom pointer more persuasive (as requested by a user).
635    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
636        pcretest.c, inside #ifndefs, because it seems they are sometimes already
637        pre-defined.
639    28. Added support for (*UTF8) at the start of a pattern.
641    29. Arrange for flags added by the "release type" setting in CMake to be shown
642        in the configuration summary.
645  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
646  ---------------------  ---------------------

Removed from v.389  
changed lines
  Added in v.565

  ViewVC Help
Powered by ViewVC 1.1.5