ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 392 by ph10, Tue Mar 17 21:30:30 2009 UTC revision 595 by ph10, Mon May 2 10:33:29 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.9 xx-xxx-09  Version 8.13 30-Apr-2011
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
25    Version 8.12 15-Jan-2011
26    ------------------------
28    1.  Fixed some typos in the markup of the man pages, and wrote a script that
29        checks for such things as part of the documentation building process.
31    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
32        --match-limit and --recursion-limit options (added for 8.11). In
33        particular, this made one of the standard tests fail. (The integer value
34        went into the wrong half of a long int.)
36    3.  If the --colour option was given to pcregrep with -v (invert match), it
37        did strange things, either producing crazy output, or crashing. It should,
38        of course, ignore a request for colour when reporting lines that do not
39        match.
41    4.  Another pcregrep bug caused similar problems if --colour was specified with
42        -M (multiline) and the pattern match finished with a line ending.
44    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
45        matched in multiline mode, the following line was shown as part of the
46        match. This seems wrong, so I have changed it.
48    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
49        the check for further matches in the same line (so they could be coloured)
50        to overrun the end of the current line. If another match was found, it was
51        incorrectly shown (and then shown again when found in the next line).
53    7.  If pcregrep was compiled under Windows, there was a reference to the
54        function pcregrep_exit() before it was defined. I am assuming this was
55        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
56        reported by a user. I've moved the definition above the reference.
59    Version 8.11 10-Dec-2010
60    ------------------------
62    1.  (*THEN) was not working properly if there were untried alternatives prior
63        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
64        backtracked to try for "b" instead of moving to the next alternative branch
65        at the same level (in this case, to look for "c"). The Perl documentation
66        is clear that when (*THEN) is backtracked onto, it goes to the "next
67        alternative in the innermost enclosing group".
69    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
70        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
71        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
72        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
73        (*THEN).
75    3.  If \s appeared in a character class, it removed the VT character from
76        the class, even if it had been included by some previous item, for example
77        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
78        of \s, but is part of the POSIX "space" class.)
80    4.  A partial match never returns an empty string (because you can always
81        match an empty string at the end of the subject); however the checking for
82        an empty string was starting at the "start of match" point. This has been
83        changed to the "earliest inspected character" point, because the returned
84        data for a partial match starts at this character. This means that, for
85        example, /(?<=abc)def/ gives a partial match for the subject "abc"
86        (previously it gave "no match").
88    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
89        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
90        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
91        has an implication that the given string is incomplete (because a partial
92        match is preferred over a full match). For this reason, these items now
93        give a partial match in this situation. [Aside: previously, the one case
94        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
95        match rather than a full match, which was wrong by the old rules, but is
96        now correct.]
98    6.  There was a bug in the handling of #-introduced comments, recognized when
99        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
100        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
101        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
102        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
103        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
104        places in pcre_compile().
106    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
107        comments when looking ahead for named forward references to subpatterns,
108        the only newline sequence it recognized was NL. It now handles newlines
109        according to the set newline convention.
111    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
112        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
113        cater for a lack of strerror(). These oversights have been fixed.
115    9.  Added --match-limit and --recursion-limit to pcregrep.
117    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
119    11. When the -o option was used, pcregrep was setting a return code of 1, even
120        when matches were found, and --line-buffered was not being honoured.
122    12. Added an optional parentheses number to the -o and --only-matching options
123        of pcregrep.
125    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
126        can match an empty string. The code to do it in pcretest and pcredemo
127        needed fixing:
129        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
130            only one byte after an empty string match just before CRLF (this case
131            just got forgotten; "any" and "anycrlf" were OK).
133        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
134            mode when an empty string match preceded an ASCII character followed by
135            a non-ASCII character. (The code for advancing by one character rather
136            than one byte was nonsense.)
138        (c) The pcredemo.c sample program did not have any code at all to handle
139            the cases when CRLF is a valid newline sequence.
141    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
142        as a starting offset was within the subject string. There is now a new
143        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
144        negative or greater than the length of the string. In order to test this,
145        pcretest is extended to allow the setting of negative starting offsets.
147    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
148        starting offset points to the beginning of a UTF-8 character was
149        unnecessarily clumsy. I tidied it up.
151    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
152        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
154    17. Nobody had reported that the --include_dir option, which was added in
155        release 7.7 should have been called --include-dir (hyphen, not underscore)
156        for compatibility with GNU grep. I have changed it to --include-dir, but
157        left --include_dir as an undocumented synonym, and the same for
158        --exclude-dir, though that is not available in GNU grep, at least as of
159        release 2.5.4.
161    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
162        characters from a string of bytes) have been redefined so as not to use
163        loops, in order to improve performance in some environments. At the same
164        time, I abstracted some of the common code into auxiliary macros to save
165        repetition (this should not affect the compiled code).
167    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
168        compile-time error is now given if \c is not followed by an ASCII
169        character, that is, a byte less than 128. (In EBCDIC mode, the code is
170        different, and any byte value is allowed.)
172    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
173        START_OPTIMIZE option, which is now allowed at compile time - but just
174        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
175        to pcregrep and other applications that have no direct access to PCRE
176        options. The new /Y option in pcretest sets this option when calling
177        pcre_compile().
179    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
180        back references. Groups containing recursive back references were forced to
181        be atomic by that change, but in the case of named groups, the amount of
182        memory required was incorrectly computed, leading to "Failed: internal
183        error: code overflow". This has been fixed.
185    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
186        pcretest.c, to avoid build problems in some Borland environments.
189    Version 8.10 25-Jun-2010
190    ------------------------
192    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
193        THEN.
195    2.  (*ACCEPT) was not working when inside an atomic group.
197    3.  Inside a character class, \B is treated as a literal by default, but
198        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
199        causes the error). The code is unchanged, but I tidied the documentation.
201    4.  Inside a character class, PCRE always treated \R and \X as literals,
202        whereas Perl faults them if its -w option is set. I have changed PCRE so
203        that it faults them when PCRE_EXTRA is set.
205    5.  Added support for \N, which always matches any character other than
206        newline. (It is the same as "." when PCRE_DOTALL is not set.)
208    6.  When compiling pcregrep with newer versions of gcc which may have
209        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
210        declared with attribute warn_unused_result" were given. Just casting the
211        result to (void) does not stop the warnings; a more elaborate fudge is
212        needed. I've used a macro to implement this.
214    7.  Minor change to pcretest.c to avoid a compiler warning.
216    8.  Added four artifical Unicode properties to help with an option to make
217        \s etc use properties (see next item). The new properties are: Xan
218        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
220    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
221        use Unicode properties. (*UCP) at the start of a pattern can be used to set
222        this option. Modified pcretest to add /W to test this facility. Added
223        REG_UCP to make it available via the POSIX interface.
225    10. Added --line-buffered to pcregrep.
227    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
228        studied, and the match started with a letter with a code point greater than
229        127 whose first byte was different to the first byte of the other case of
230        the letter, the other case of this starting letter was not recognized
231        (#976).
233    12. If a pattern that was studied started with a repeated Unicode property
234        test, for example, \p{Nd}+, there was the theoretical possibility of
235        setting up an incorrect bitmap of starting bytes, but fortunately it could
236        not have actually happened in practice until change 8 above was made (it
237        added property types that matched character-matching opcodes).
239    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
240        possible starting bytes for non-anchored patterns.
242    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
243        \R, and also a number of cases that involve Unicode properties, both
244        explicit and implicit when PCRE_UCP is set.
246    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
247        input, it could crash or give wrong results if characters with values
248        greater than 0xc0 were present in the subject string. (Detail: it assumed
249        UTF-8 input when processing these items.)
251    16. Added a lot of (int) casts to avoid compiler warnings in systems where
252        size_t is 64-bit (#991).
254    17. Added a check for running out of memory when PCRE is compiled with
255        --disable-stack-for-recursion (#990).
257    18. If the last data line in a file for pcretest does not have a newline on
258        the end, a newline was missing in the output.
260    19. The default pcre_chartables.c file recognizes only ASCII characters (values
261        less than 128) in its various bitmaps. However, there is a facility for
262        generating tables according to the current locale when PCRE is compiled. It
263        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
264        characters, are recognized by isspace() and therefore were getting set in
265        these tables, and indeed these tables seem to approximate to ISO 8859. This
266        caused a problem in UTF-8 mode when pcre_study() was used to create a list
267        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
268        which of course cannot start UTF-8 characters. I have changed the code so
269        that only real ASCII characters (less than 128) and the correct starting
270        bytes for UTF-8 encodings are set for characters greater than 127 when in
271        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
272        altogether.)
274    20. Added the /T option to pcretest so as to be able to run tests with non-
275        standard character tables, thus making it possible to include the tests
276        used for 19 above in the standard set of tests.
278    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
279        reference to a subpattern the other side of a comment that contains an
280        opening parenthesis caused either an internal compiling error, or a
281        reference to the wrong subpattern.
284    Version 8.02 19-Mar-2010
285    ------------------------
287    1.  The Unicode data tables have been updated to Unicode 5.2.0.
289    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
290        configured.
292    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
293        original author of that file, following a query about its status.
295    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
296        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
298    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
299        quantifier applied to a forward-referencing subroutine call, could compile
300        incorrect code or give the error "internal error: previously-checked
301        referenced subpattern not found".
303    6.  Both MS Visual Studio and Symbian OS have problems with initializing
304        variables to point to external functions. For these systems, therefore,
305        pcre_malloc etc. are now initialized to local functions that call the
306        relevant global functions.
308    7.  There were two entries missing in the vectors called coptable and poptable
309        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
310        I've fixed the data, and added a kludgy way of testing at compile time that
311        the lengths are correct (equal to the number of opcodes).
313    8.  Following on from 7, I added a similar kludge to check the length of the
314        eint vector in pcreposix.c.
316    9.  Error texts for pcre_compile() are held as one long string to avoid too
317        much relocation at load time. To find a text, the string is searched,
318        counting zeros. There was no check for running off the end of the string,
319        which could happen if a new error number was added without updating the
320        string.
322    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
324    11. \K was not working if it appeared in an atomic group or in a group that
325        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
326        \K is "not well defined" if used in an assertion. PCRE now accepts it if
327        the assertion is positive, but not if it is negative.
329    12. Change 11 fortuitously reduced the size of the stack frame used in the
330        "match()" function of pcre_exec.c by one pointer. Forthcoming
331        implementation of support for (*MARK) will need an extra pointer on the
332        stack; I have reserved it now, so that the stack frame size does not
333        decrease.
335    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
336        item in branch that calls a recursion is a subroutine call - as in the
337        second branch in the above example - was incorrectly given the compile-
338        time error "recursive call could loop indefinitely" because pcre_compile()
339        was not correctly checking the subroutine for matching a non-empty string.
341    14. The checks for overrunning compiling workspace could trigger after an
342        overrun had occurred. This is a "should never occur" error, but it can be
343        triggered by pathological patterns such as hundreds of nested parentheses.
344        The checks now trigger 100 bytes before the end of the workspace.
346    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
349    Version 8.01 19-Jan-2010
350    ------------------------
352    1.  If a pattern contained a conditional subpattern with only one branch (in
353        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
354        computed the wrong minimum data length (which is of course zero for such
355        subpatterns). This could cause incorrect "no match" results.
357    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
358        the pattern is reset in the first branch, pcre_compile() failed with
359        "internal error: code overflow at offset...". This happened only when
360        the reset was to the original external option setting. (An optimization
361        abstracts leading options settings into an external setting, which was the
362        cause of this.)
364    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
365        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
366        assertion pattern did not match (meaning that the assertion was true), it
367        was incorrectly treated as false if the SKIP had been reached during the
368        matching. This also applied to assertions used as conditions.
370    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
371        assertion subpattern, including such a pattern used as a condition,
372        unpredictable results occurred, instead of the error return
375    5.  The C++ GlobalReplace function was not working like Perl for the special
376        situation when an empty string is matched. It now does the fancy magic
377        stuff that is necessary.
379    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
380        removed. (These were left over from very, very early versions of PCRE.)
382    7.  Some cosmetic changes to the code to make life easier when compiling it
383        as part of something else:
385        (a) Change DEBUG to PCRE_DEBUG.
387        (b) In pcre_compile(), rename the member of the "branch_chain" structure
388            called "current" as "current_branch", to prevent a collision with the
389            Linux macro when compiled as a kernel module.
391        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
392            prevent a collision with the Linux macro when compiled as a kernel
393            module.
395    8.  In pcre_compile() there are some checks for integer overflows that used to
396        cast potentially large values to (double). This has been changed to that
397        when building, a check for int64_t is made, and if it is found, it is used
398        instead, thus avoiding the use of floating point arithmetic. (There is no
399        other use of FP in PCRE.) If int64_t is not found, the fallback is to
400        double.
402    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
403        2005 (difference between two addresses compared to an unsigned value).
405    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
406        custom one, because of the following reported problem in Windows:
408          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
409              under Win32.
410          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
411              therefore missing the function definition.
412          - The compiler thus generates a "C" signature for the test function.
413          - The linker fails to find the "C" function.
414          - PCRE fails to configure if asked to do so against libbz2.
416    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
417        messages were output:
419          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
420          rerunning libtoolize, to keep the correct libtool macros in-tree.
421          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
423        I have done both of these things.
425    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
426        most of the time, it *can* run out if it is given a pattern that contains a
427        runaway infinite recursion. I updated the discussion in the pcrestack man
428        page.
430    13. Now that we have gone to the x.xx style of version numbers, the minor
431        version may start with zero. Using 08 or 09 is a bad idea because users
432        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
433        interpreted as invalid octal numbers. I've updated the previous comment in
434        configure.ac, and also added a check that gives an error if 08 or 09 are
435        used.
437    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
438        causing partial matching to fail when the end of the subject matched \W
439        in a UTF-8 pattern where \W was quantified with a minimum of 3.
441    15. There were some discrepancies between the declarations in pcre_internal.h
442        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
443        their definitions. The declarations used "const uschar *" and the
444        definitions used USPTR. Even though USPTR is normally defined as "const
445        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
446        reported that: "This difference in casting confuses some C++ compilers, for
447        example, SunCC recognizes above declarations as different functions and
448        generates broken code for hbpcre." I have changed the declarations to use
449        USPTR.
451    16. GNU libtool is named differently on some systems. The autogen.sh script now
452        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
453        (FreeBSD).
455    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
456        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
457        comment: "Figure out how to create a longlong from a string: strtoll and
458        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
459        instance, but it only takes 2 args instead of 3!"
461    18. A subtle bug concerned with back references has been fixed by a change of
462        specification, with a corresponding code fix. A pattern such as
463        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
464        refers, was giving matches when it shouldn't. For example, xa=xaaa would
465        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
466        same bug. Such groups have to be quantified to be useful, or contained
467        inside another quantified group. (If there's no repetition, the reference
468        can never match.) The problem arises because, having left the group and
469        moved on to the rest of the pattern, a later failure that backtracks into
470        the group uses the captured value from the final iteration of the group
471        rather than the correct earlier one. I have fixed this in PCRE by forcing
472        any group that contains a reference to itself to be an atomic group; that
473        is, there cannot be any backtracking into it once it has completed. This is
474        similar to recursive and subroutine calls.
477    Version 8.00 19-Oct-09
478    ----------------------
480    1.  The table for translating pcre_compile() error codes into POSIX error codes
481        was out-of-date, and there was no check on the pcre_compile() error code
482        being within the table. This could lead to an OK return being given in
483        error.
485    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
486        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
487        in a Windows environment.
489    3.  The pcregrep --count option prints the count for each file even when it is
490        zero, as does GNU grep. However, pcregrep was also printing all files when
491        --files-with-matches was added. Now, when both options are given, it prints
492        counts only for those files that have at least one match. (GNU grep just
493        prints the file name in this circumstance, but including the count seems
494        more useful - otherwise, why use --count?) Also ensured that the
495        combination -clh just lists non-zero counts, with no names.
497    4.  The long form of the pcregrep -F option was incorrectly implemented as
498        --fixed_strings instead of --fixed-strings. This is an incompatible change,
499        but it seems right to fix it, and I didn't think it was worth preserving
500        the old behaviour.
502    5.  The command line items --regex=pattern and --regexp=pattern were not
503        recognized by pcregrep, which required --regex pattern or --regexp pattern
504        (with a space rather than an '='). The man page documented the '=' forms,
505        which are compatible with GNU grep; these now work.
507    6.  No libpcreposix.pc file was created for pkg-config; there was just
508        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
510    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
511        when UCP support is not needed, by modifying the Python script that
512        generates it from Unicode data files. This should not matter if the module
513        is correctly used as a library, but I received one complaint about 50K of
514        unwanted data. My guess is that the person linked everything into his
515        program rather than using a library. Anyway, it does no harm.
517    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
518        was a minimum greater than 1 for a wide character in a possessive
519        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
520        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
521        character. Chaos in the form of incorrect output or a compiling loop could
522        result.
524    9.  The restrictions on what a pattern can contain when partial matching is
525        requested for pcre_exec() have been removed. All patterns can now be
526        partially matched by this function. In addition, if there are at least two
527        slots in the offset vector, the offset of the earliest inspected character
528        for the match and the offset of the end of the subject are set in them when
529        PCRE_ERROR_PARTIAL is returned.
531    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
532        synonymous with PCRE_PARTIAL, for backwards compatibility, and
533        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
534        and may be more useful for multi-segment matching.
536    11. Partial matching with pcre_exec() is now more intuitive. A partial match
537        used to be given if ever the end of the subject was reached; now it is
538        given only if matching could not proceed because another character was
539        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
540        string "Z", which now yields "no match" instead of "partial match". In the
541        case of pcre_dfa_exec(), "no match" is given if every matching path for the
542        final character ended with (*FAIL).
544    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
545        if the pattern had a "must contain" character that was already found in the
546        earlier partial match, unless partial matching was again requested. For
547        example, with the pattern /dog.(body)?/, the "must contain" character is
548        "g". If the first part-match was for the string "dog", restarting with
549        "sbody" failed. This bug has been fixed.
551    13. The string returned by pcre_dfa_exec() after a partial match has been
552        changed so that it starts at the first inspected character rather than the
553        first character of the match. This makes a difference only if the pattern
554        starts with a lookbehind assertion or \b or \B (\K is not supported by
555        pcre_dfa_exec()). It's an incompatible change, but it makes the two
556        matching functions compatible, and I think it's the right thing to do.
558    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
559        so that the demonstration program is easily available in environments where
560        PCRE has not been installed from source.
562    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
563        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
564        library.
566    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
567        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
568        is not the first non-POSIX option to be added. Clearly some people find
569        these options useful.
571    17. If a caller to the POSIX matching function regexec() passes a non-zero
572        value for nmatch with a NULL value for pmatch, the value of
573        nmatch is forced to zero.
575    18. RunGrepTest did not have a test for the availability of the -u option of
576        the diff command, as RunTest does. It now checks in the same way as
577        RunTest, and also checks for the -b option.
579    19. If an odd number of negated classes containing just a single character
580        interposed, within parentheses, between a forward reference to a named
581        subpattern and the definition of the subpattern, compilation crashed with
582        an internal error, complaining that it could not find the referenced
583        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
584        [The bug was that it was starting one character too far in when skipping
585        over the character class, thus treating the ] as data rather than
586        terminating the class. This meant it could skip too much.]
588    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
589        /g option in pcretest when the pattern contains \K, which makes it possible
590        to have an empty string match not at the start, even when the pattern is
591        anchored. Updated pcretest and pcredemo to use this option.
593    21. If the maximum number of capturing subpatterns in a recursion was greater
594        than the maximum at the outer level, the higher number was returned, but
595        with unset values at the outer level. The correct (outer level) value is
596        now given.
598    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
599        PCRE did not set those parentheses (unlike Perl). I have now found a way to
600        make it do so. The string so far is captured, making this feature
601        compatible with Perl.
603    23. The tests have been re-organized, adding tests 11 and 12, to make it
604        possible to check the Perl 5.10 features against Perl 5.10.
606    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
607        pattern matches a fixed length string. PCRE did not allow this; now it
608        does. Neither allows recursion.
610    25. I finally figured out how to implement a request to provide the minimum
611        length of subject string that was needed in order to match a given pattern.
612        (It was back references and recursion that I had previously got hung up
613        on.) This code has now been added to pcre_study(); it finds a lower bound
614        to the length of subject needed. It is not necessarily the greatest lower
615        bound, but using it to avoid searching strings that are too short does give
616        some useful speed-ups. The value is available to calling programs via
617        pcre_fullinfo().
619    26. While implementing 25, I discovered to my embarrassment that pcretest had
620        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
621        study optimizations had never been tested with that matching function.
622        Oops. What is worse, even when it was passed study data, there was a bug in
623        pcre_dfa_exec() that meant it never actually used it. Double oops. There
624        were also very few tests of studied patterns with pcre_dfa_exec().
626    27. If (?| is used to create subpatterns with duplicate numbers, they are now
627        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
628        on the other side of the coin, they are no longer allowed to have different
629        names, because these cannot be distinguished in PCRE, and this has caused
630        confusion. (This is a difference from Perl.)
632    28. When duplicate subpattern names are present (necessarily with different
633        numbers, as required by 27 above), and a test is made by name in a
634        conditional pattern, either for a subpattern having been matched, or for
635        recursion in such a pattern, all the associated numbered subpatterns are
636        tested, and the overall condition is true if the condition is true for any
637        one of them. This is the way Perl works, and is also more like the way
638        testing by number works.
641    Version 7.9 11-Apr-09
642  ---------------------  ---------------------
644  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 654  Version 7.9 xx-xxx-09
654      but BOOL is not.      but BOOL is not.
656  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
657      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.
659  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
660      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 42  Version 7.9 xx-xxx-09 Line 679  Version 7.9 xx-xxx-09
679      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
680      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
682  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
683      could crash during matching.      condition was an assertion, PCRE could crash during matching, both with
684        pcre_exec() and pcre_dfa_exec().
686  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was  10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
687      used for matching.      used for matching.
# Line 64  Version 7.9 xx-xxx-09 Line 702  Version 7.9 xx-xxx-09
702      from Martin Jerabek that uses macro names for all relevant character and      from Martin Jerabek that uses macro names for all relevant character and
703      string constants.      string constants.
705    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
706        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
707        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
708        these, but not everybody uses configure.
710    19. A conditional group that had only one branch was not being correctly
711        recognized as an item that could match an empty string. This meant that an
712        enclosing group might also not be so recognized, causing infinite looping
713        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
714        with the subject "ab", where knowledge that the repeated group can match
715        nothing is needed in order to break the loop.
717    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
718        exec(), but without supplying a callout function, matching went wrong.
720    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
721        leak if the size of the offset vector was greater than 30. When the vector
722        is smaller, the saved offsets during recursion go onto a local stack
723        vector, but for larger vectors malloc() is used. It was failing to free
724        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
725        error, in fact).
727    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
728        heapframe that is used only when UTF-8 support is enabled. This caused no
729        problem, but was untidy.
731    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
732        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
733        included within another project.
735    24. Steven Van Ingelgem's patches to add more options to the CMake support,
736        slightly modified by me:
738          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
739              not building pcregrep.
741          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
742              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
744    25. Forward references, both numeric and by name, in patterns that made use of
745        duplicate group numbers, could behave incorrectly or give incorrect errors,
746        because when scanning forward to find the reference group, PCRE was not
747        taking into account the duplicate group numbers. A pattern such as
748        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
750    26. Changed a few more instances of "const unsigned char *" to USPTR, making
751        the feature of a custom pointer more persuasive (as requested by a user).
753    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
754        pcretest.c, inside #ifndefs, because it seems they are sometimes already
755        pre-defined.
757    28. Added support for (*UTF8) at the start of a pattern.
759    29. Arrange for flags added by the "release type" setting in CMake to be shown
760        in the configuration summary.
763  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
764  ---------------------  ---------------------

Removed from v.392  
changed lines
  Added in v.595

  ViewVC Help
Powered by ViewVC 1.1.5