ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 319 by ph10, Mon Jan 28 15:27:45 2008 UTC revision 587 by ph10, Fri Jan 14 19:01:25 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4    Version 8.12 12-Jan-2011
5    ------------------------
7    1.  Fixed some typos in the markup of the man pages, and wrote a script that
8        checks for such things as part of the documentation building process.
10    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
11        --match-limit and --recursion-limit options (added for 8.11). In
12        particular, this made one of the standard tests crash. (The integer value
13        went into the wrong half of a long int.)
15    3.  If the --colour option was given to pcregrep with -v (invert match), it
16        did strange things, either producing crazy output, or crashing. It should,
17        of course, ignore a request for colour when reporting lines that do not
18        match.
20    4.  Another pcregrep bug caused similar problems if --colour was specified with
21        -M (multiline) and the pattern match finished with a line ending.
23    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
24        matched in multiline mode, the following line was shown as part of the
25        match. This seems wrong, so I have changed it.
27    6.  If pcregrep was compiled under Windows, there was a reference to the
28        function pcregrep_exit() before it was defined. I am assuming this was
29        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
30        reported by a user. I've moved the definition above the reference.
33    Version 8.11 10-Dec-2010
34    ------------------------
36    1.  (*THEN) was not working properly if there were untried alternatives prior
37        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
38        backtracked to try for "b" instead of moving to the next alternative branch
39        at the same level (in this case, to look for "c"). The Perl documentation
40        is clear that when (*THEN) is backtracked onto, it goes to the "next
41        alternative in the innermost enclosing group".
43    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
44        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
45        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
46        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
47        (*THEN).
49    3.  If \s appeared in a character class, it removed the VT character from
50        the class, even if it had been included by some previous item, for example
51        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
52        of \s, but is part of the POSIX "space" class.)
54    4.  A partial match never returns an empty string (because you can always
55        match an empty string at the end of the subject); however the checking for
56        an empty string was starting at the "start of match" point. This has been
57        changed to the "earliest inspected character" point, because the returned
58        data for a partial match starts at this character. This means that, for
59        example, /(?<=abc)def/ gives a partial match for the subject "abc"
60        (previously it gave "no match").
62    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
63        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
64        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
65        has an implication that the given string is incomplete (because a partial
66        match is preferred over a full match). For this reason, these items now
67        give a partial match in this situation. [Aside: previously, the one case
68        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
69        match rather than a full match, which was wrong by the old rules, but is
70        now correct.]
72    6.  There was a bug in the handling of #-introduced comments, recognized when
73        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
74        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
75        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
76        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
77        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
78        places in pcre_compile().
80    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
81        comments when looking ahead for named forward references to subpatterns,
82        the only newline sequence it recognized was NL. It now handles newlines
83        according to the set newline convention.
85    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
86        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
87        cater for a lack of strerror(). These oversights have been fixed.
89    9.  Added --match-limit and --recursion-limit to pcregrep.
91    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
93    11. When the -o option was used, pcregrep was setting a return code of 1, even
94        when matches were found, and --line-buffered was not being honoured.
96    12. Added an optional parentheses number to the -o and --only-matching options
97        of pcregrep.
99    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
100        can match an empty string. The code to do it in pcretest and pcredemo
101        needed fixing:
103        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
104            only one byte after an empty string match just before CRLF (this case
105            just got forgotten; "any" and "anycrlf" were OK).
107        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
108            mode when an empty string match preceded an ASCII character followed by
109            a non-ASCII character. (The code for advancing by one character rather
110            than one byte was nonsense.)
112        (c) The pcredemo.c sample program did not have any code at all to handle
113            the cases when CRLF is a valid newline sequence.
115    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
116        as a starting offset was within the subject string. There is now a new
117        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
118        negative or greater than the length of the string. In order to test this,
119        pcretest is extended to allow the setting of negative starting offsets.
121    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
122        starting offset points to the beginning of a UTF-8 character was
123        unnecessarily clumsy. I tidied it up.
125    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
126        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
128    17. Nobody had reported that the --include_dir option, which was added in
129        release 7.7 should have been called --include-dir (hyphen, not underscore)
130        for compatibility with GNU grep. I have changed it to --include-dir, but
131        left --include_dir as an undocumented synonym, and the same for
132        --exclude-dir, though that is not available in GNU grep, at least as of
133        release 2.5.4.
135    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
136        characters from a string of bytes) have been redefined so as not to use
137        loops, in order to improve performance in some environments. At the same
138        time, I abstracted some of the common code into auxiliary macros to save
139        repetition (this should not affect the compiled code).
141    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
142        compile-time error is now given if \c is not followed by an ASCII
143        character, that is, a byte less than 128. (In EBCDIC mode, the code is
144        different, and any byte value is allowed.)
146    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
147        START_OPTIMIZE option, which is now allowed at compile time - but just
148        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
149        to pcregrep and other applications that have no direct access to PCRE
150        options. The new /Y option in pcretest sets this option when calling
151        pcre_compile().
153    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
154        back references. Groups containing recursive back references were forced to
155        be atomic by that change, but in the case of named groups, the amount of
156        memory required was incorrectly computed, leading to "Failed: internal
157        error: code overflow". This has been fixed.
159    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
160        pcretest.c, to avoid build problems in some Borland environments.
163    Version 8.10 25-Jun-2010
164    ------------------------
166    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
167        THEN.
169    2.  (*ACCEPT) was not working when inside an atomic group.
171    3.  Inside a character class, \B is treated as a literal by default, but
172        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
173        causes the error). The code is unchanged, but I tidied the documentation.
175    4.  Inside a character class, PCRE always treated \R and \X as literals,
176        whereas Perl faults them if its -w option is set. I have changed PCRE so
177        that it faults them when PCRE_EXTRA is set.
179    5.  Added support for \N, which always matches any character other than
180        newline. (It is the same as "." when PCRE_DOTALL is not set.)
182    6.  When compiling pcregrep with newer versions of gcc which may have
183        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
184        declared with attribute warn_unused_result" were given. Just casting the
185        result to (void) does not stop the warnings; a more elaborate fudge is
186        needed. I've used a macro to implement this.
188    7.  Minor change to pcretest.c to avoid a compiler warning.
190    8.  Added four artifical Unicode properties to help with an option to make
191        \s etc use properties (see next item). The new properties are: Xan
192        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
194    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
195        use Unicode properties. (*UCP) at the start of a pattern can be used to set
196        this option. Modified pcretest to add /W to test this facility. Added
197        REG_UCP to make it available via the POSIX interface.
199    10. Added --line-buffered to pcregrep.
201    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
202        studied, and the match started with a letter with a code point greater than
203        127 whose first byte was different to the first byte of the other case of
204        the letter, the other case of this starting letter was not recognized
205        (#976).
207    12. If a pattern that was studied started with a repeated Unicode property
208        test, for example, \p{Nd}+, there was the theoretical possibility of
209        setting up an incorrect bitmap of starting bytes, but fortunately it could
210        not have actually happened in practice until change 8 above was made (it
211        added property types that matched character-matching opcodes).
213    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
214        possible starting bytes for non-anchored patterns.
216    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
217        \R, and also a number of cases that involve Unicode properties, both
218        explicit and implicit when PCRE_UCP is set.
220    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
221        input, it could crash or give wrong results if characters with values
222        greater than 0xc0 were present in the subject string. (Detail: it assumed
223        UTF-8 input when processing these items.)
225    16. Added a lot of (int) casts to avoid compiler warnings in systems where
226        size_t is 64-bit (#991).
228    17. Added a check for running out of memory when PCRE is compiled with
229        --disable-stack-for-recursion (#990).
231    18. If the last data line in a file for pcretest does not have a newline on
232        the end, a newline was missing in the output.
234    19. The default pcre_chartables.c file recognizes only ASCII characters (values
235        less than 128) in its various bitmaps. However, there is a facility for
236        generating tables according to the current locale when PCRE is compiled. It
237        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
238        characters, are recognized by isspace() and therefore were getting set in
239        these tables, and indeed these tables seem to approximate to ISO 8859. This
240        caused a problem in UTF-8 mode when pcre_study() was used to create a list
241        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
242        which of course cannot start UTF-8 characters. I have changed the code so
243        that only real ASCII characters (less than 128) and the correct starting
244        bytes for UTF-8 encodings are set for characters greater than 127 when in
245        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
246        altogether.)
248    20. Added the /T option to pcretest so as to be able to run tests with non-
249        standard character tables, thus making it possible to include the tests
250        used for 19 above in the standard set of tests.
252    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
253        reference to a subpattern the other side of a comment that contains an
254        opening parenthesis caused either an internal compiling error, or a
255        reference to the wrong subpattern.
258    Version 8.02 19-Mar-2010
259    ------------------------
261    1.  The Unicode data tables have been updated to Unicode 5.2.0.
263    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
264        configured.
266    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
267        original author of that file, following a query about its status.
269    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
270        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
272    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
273        quantifier applied to a forward-referencing subroutine call, could compile
274        incorrect code or give the error "internal error: previously-checked
275        referenced subpattern not found".
277    6.  Both MS Visual Studio and Symbian OS have problems with initializing
278        variables to point to external functions. For these systems, therefore,
279        pcre_malloc etc. are now initialized to local functions that call the
280        relevant global functions.
282    7.  There were two entries missing in the vectors called coptable and poptable
283        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
284        I've fixed the data, and added a kludgy way of testing at compile time that
285        the lengths are correct (equal to the number of opcodes).
287    8.  Following on from 7, I added a similar kludge to check the length of the
288        eint vector in pcreposix.c.
290    9.  Error texts for pcre_compile() are held as one long string to avoid too
291        much relocation at load time. To find a text, the string is searched,
292        counting zeros. There was no check for running off the end of the string,
293        which could happen if a new error number was added without updating the
294        string.
296    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
298    11. \K was not working if it appeared in an atomic group or in a group that
299        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
300        \K is "not well defined" if used in an assertion. PCRE now accepts it if
301        the assertion is positive, but not if it is negative.
303    12. Change 11 fortuitously reduced the size of the stack frame used in the
304        "match()" function of pcre_exec.c by one pointer. Forthcoming
305        implementation of support for (*MARK) will need an extra pointer on the
306        stack; I have reserved it now, so that the stack frame size does not
307        decrease.
309    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
310        item in branch that calls a recursion is a subroutine call - as in the
311        second branch in the above example - was incorrectly given the compile-
312        time error "recursive call could loop indefinitely" because pcre_compile()
313        was not correctly checking the subroutine for matching a non-empty string.
315    14. The checks for overrunning compiling workspace could trigger after an
316        overrun had occurred. This is a "should never occur" error, but it can be
317        triggered by pathological patterns such as hundreds of nested parentheses.
318        The checks now trigger 100 bytes before the end of the workspace.
320    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
323    Version 8.01 19-Jan-2010
324    ------------------------
326    1.  If a pattern contained a conditional subpattern with only one branch (in
327        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
328        computed the wrong minimum data length (which is of course zero for such
329        subpatterns). This could cause incorrect "no match" results.
331    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
332        the pattern is reset in the first branch, pcre_compile() failed with
333        "internal error: code overflow at offset...". This happened only when
334        the reset was to the original external option setting. (An optimization
335        abstracts leading options settings into an external setting, which was the
336        cause of this.)
338    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
339        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
340        assertion pattern did not match (meaning that the assertion was true), it
341        was incorrectly treated as false if the SKIP had been reached during the
342        matching. This also applied to assertions used as conditions.
344    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
345        assertion subpattern, including such a pattern used as a condition,
346        unpredictable results occurred, instead of the error return
349    5.  The C++ GlobalReplace function was not working like Perl for the special
350        situation when an empty string is matched. It now does the fancy magic
351        stuff that is necessary.
353    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
354        removed. (These were left over from very, very early versions of PCRE.)
356    7.  Some cosmetic changes to the code to make life easier when compiling it
357        as part of something else:
359        (a) Change DEBUG to PCRE_DEBUG.
361        (b) In pcre_compile(), rename the member of the "branch_chain" structure
362            called "current" as "current_branch", to prevent a collision with the
363            Linux macro when compiled as a kernel module.
365        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
366            prevent a collision with the Linux macro when compiled as a kernel
367            module.
369    8.  In pcre_compile() there are some checks for integer overflows that used to
370        cast potentially large values to (double). This has been changed to that
371        when building, a check for int64_t is made, and if it is found, it is used
372        instead, thus avoiding the use of floating point arithmetic. (There is no
373        other use of FP in PCRE.) If int64_t is not found, the fallback is to
374        double.
376    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
377        2005 (difference between two addresses compared to an unsigned value).
379    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
380        custom one, because of the following reported problem in Windows:
382          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
383              under Win32.
384          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
385              therefore missing the function definition.
386          - The compiler thus generates a "C" signature for the test function.
387          - The linker fails to find the "C" function.
388          - PCRE fails to configure if asked to do so against libbz2.
390    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
391        messages were output:
393          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
394          rerunning libtoolize, to keep the correct libtool macros in-tree.
395          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
397        I have done both of these things.
399    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
400        most of the time, it *can* run out if it is given a pattern that contains a
401        runaway infinite recursion. I updated the discussion in the pcrestack man
402        page.
404    13. Now that we have gone to the x.xx style of version numbers, the minor
405        version may start with zero. Using 08 or 09 is a bad idea because users
406        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
407        interpreted as invalid octal numbers. I've updated the previous comment in
408        configure.ac, and also added a check that gives an error if 08 or 09 are
409        used.
411    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
412        causing partial matching to fail when the end of the subject matched \W
413        in a UTF-8 pattern where \W was quantified with a minimum of 3.
415    15. There were some discrepancies between the declarations in pcre_internal.h
416        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
417        their definitions. The declarations used "const uschar *" and the
418        definitions used USPTR. Even though USPTR is normally defined as "const
419        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
420        reported that: "This difference in casting confuses some C++ compilers, for
421        example, SunCC recognizes above declarations as different functions and
422        generates broken code for hbpcre." I have changed the declarations to use
423        USPTR.
425    16. GNU libtool is named differently on some systems. The autogen.sh script now
426        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
427        (FreeBSD).
429    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
430        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
431        comment: "Figure out how to create a longlong from a string: strtoll and
432        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
433        instance, but it only takes 2 args instead of 3!"
435    18. A subtle bug concerned with back references has been fixed by a change of
436        specification, with a corresponding code fix. A pattern such as
437        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
438        refers, was giving matches when it shouldn't. For example, xa=xaaa would
439        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
440        same bug. Such groups have to be quantified to be useful, or contained
441        inside another quantified group. (If there's no repetition, the reference
442        can never match.) The problem arises because, having left the group and
443        moved on to the rest of the pattern, a later failure that backtracks into
444        the group uses the captured value from the final iteration of the group
445        rather than the correct earlier one. I have fixed this in PCRE by forcing
446        any group that contains a reference to itself to be an atomic group; that
447        is, there cannot be any backtracking into it once it has completed. This is
448        similar to recursive and subroutine calls.
451    Version 8.00 19-Oct-09
452    ----------------------
454    1.  The table for translating pcre_compile() error codes into POSIX error codes
455        was out-of-date, and there was no check on the pcre_compile() error code
456        being within the table. This could lead to an OK return being given in
457        error.
459    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
460        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
461        in a Windows environment.
463    3.  The pcregrep --count option prints the count for each file even when it is
464        zero, as does GNU grep. However, pcregrep was also printing all files when
465        --files-with-matches was added. Now, when both options are given, it prints
466        counts only for those files that have at least one match. (GNU grep just
467        prints the file name in this circumstance, but including the count seems
468        more useful - otherwise, why use --count?) Also ensured that the
469        combination -clh just lists non-zero counts, with no names.
471    4.  The long form of the pcregrep -F option was incorrectly implemented as
472        --fixed_strings instead of --fixed-strings. This is an incompatible change,
473        but it seems right to fix it, and I didn't think it was worth preserving
474        the old behaviour.
476    5.  The command line items --regex=pattern and --regexp=pattern were not
477        recognized by pcregrep, which required --regex pattern or --regexp pattern
478        (with a space rather than an '='). The man page documented the '=' forms,
479        which are compatible with GNU grep; these now work.
481    6.  No libpcreposix.pc file was created for pkg-config; there was just
482        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
484    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
485        when UCP support is not needed, by modifying the Python script that
486        generates it from Unicode data files. This should not matter if the module
487        is correctly used as a library, but I received one complaint about 50K of
488        unwanted data. My guess is that the person linked everything into his
489        program rather than using a library. Anyway, it does no harm.
491    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
492        was a minimum greater than 1 for a wide character in a possessive
493        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
494        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
495        character. Chaos in the form of incorrect output or a compiling loop could
496        result.
498    9.  The restrictions on what a pattern can contain when partial matching is
499        requested for pcre_exec() have been removed. All patterns can now be
500        partially matched by this function. In addition, if there are at least two
501        slots in the offset vector, the offset of the earliest inspected character
502        for the match and the offset of the end of the subject are set in them when
503        PCRE_ERROR_PARTIAL is returned.
505    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
506        synonymous with PCRE_PARTIAL, for backwards compatibility, and
507        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
508        and may be more useful for multi-segment matching.
510    11. Partial matching with pcre_exec() is now more intuitive. A partial match
511        used to be given if ever the end of the subject was reached; now it is
512        given only if matching could not proceed because another character was
513        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
514        string "Z", which now yields "no match" instead of "partial match". In the
515        case of pcre_dfa_exec(), "no match" is given if every matching path for the
516        final character ended with (*FAIL).
518    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
519        if the pattern had a "must contain" character that was already found in the
520        earlier partial match, unless partial matching was again requested. For
521        example, with the pattern /dog.(body)?/, the "must contain" character is
522        "g". If the first part-match was for the string "dog", restarting with
523        "sbody" failed. This bug has been fixed.
525    13. The string returned by pcre_dfa_exec() after a partial match has been
526        changed so that it starts at the first inspected character rather than the
527        first character of the match. This makes a difference only if the pattern
528        starts with a lookbehind assertion or \b or \B (\K is not supported by
529        pcre_dfa_exec()). It's an incompatible change, but it makes the two
530        matching functions compatible, and I think it's the right thing to do.
532    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
533        so that the demonstration program is easily available in environments where
534        PCRE has not been installed from source.
536    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
537        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
538        library.
540    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
541        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
542        is not the first non-POSIX option to be added. Clearly some people find
543        these options useful.
545    17. If a caller to the POSIX matching function regexec() passes a non-zero
546        value for nmatch with a NULL value for pmatch, the value of
547        nmatch is forced to zero.
549    18. RunGrepTest did not have a test for the availability of the -u option of
550        the diff command, as RunTest does. It now checks in the same way as
551        RunTest, and also checks for the -b option.
553    19. If an odd number of negated classes containing just a single character
554        interposed, within parentheses, between a forward reference to a named
555        subpattern and the definition of the subpattern, compilation crashed with
556        an internal error, complaining that it could not find the referenced
557        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
558        [The bug was that it was starting one character too far in when skipping
559        over the character class, thus treating the ] as data rather than
560        terminating the class. This meant it could skip too much.]
562    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
563        /g option in pcretest when the pattern contains \K, which makes it possible
564        to have an empty string match not at the start, even when the pattern is
565        anchored. Updated pcretest and pcredemo to use this option.
567    21. If the maximum number of capturing subpatterns in a recursion was greater
568        than the maximum at the outer level, the higher number was returned, but
569        with unset values at the outer level. The correct (outer level) value is
570        now given.
572    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
573        PCRE did not set those parentheses (unlike Perl). I have now found a way to
574        make it do so. The string so far is captured, making this feature
575        compatible with Perl.
577    23. The tests have been re-organized, adding tests 11 and 12, to make it
578        possible to check the Perl 5.10 features against Perl 5.10.
580    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
581        pattern matches a fixed length string. PCRE did not allow this; now it
582        does. Neither allows recursion.
584    25. I finally figured out how to implement a request to provide the minimum
585        length of subject string that was needed in order to match a given pattern.
586        (It was back references and recursion that I had previously got hung up
587        on.) This code has now been added to pcre_study(); it finds a lower bound
588        to the length of subject needed. It is not necessarily the greatest lower
589        bound, but using it to avoid searching strings that are too short does give
590        some useful speed-ups. The value is available to calling programs via
591        pcre_fullinfo().
593    26. While implementing 25, I discovered to my embarrassment that pcretest had
594        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
595        study optimizations had never been tested with that matching function.
596        Oops. What is worse, even when it was passed study data, there was a bug in
597        pcre_dfa_exec() that meant it never actually used it. Double oops. There
598        were also very few tests of studied patterns with pcre_dfa_exec().
600    27. If (?| is used to create subpatterns with duplicate numbers, they are now
601        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
602        on the other side of the coin, they are no longer allowed to have different
603        names, because these cannot be distinguished in PCRE, and this has caused
604        confusion. (This is a difference from Perl.)
606    28. When duplicate subpattern names are present (necessarily with different
607        numbers, as required by 27 above), and a test is made by name in a
608        conditional pattern, either for a subpattern having been matched, or for
609        recursion in such a pattern, all the associated numbered subpatterns are
610        tested, and the overall condition is true if the condition is true for any
611        one of them. This is the way Perl works, and is also more like the way
612        testing by number works.
615    Version 7.9 11-Apr-09
616    ---------------------
618    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
619        (pcretest), all targets were linked against these libraries. This included
620        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
621        libraries. This caused unwanted dependencies to be created. This problem
622        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
623        pcretest is linked with readline.
625    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
626        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
627        moved outside it again, because FALSE and TRUE are already defined in AIX,
628        but BOOL is not.
630    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
631        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
633    4.  The pcregrep documentation said spaces were inserted as well as colons (or
634        hyphens) following file names and line numbers when outputting matching
635        lines. This is not true; no spaces are inserted. I have also clarified the
636        wording for the --colour (or --color) option.
638    5.  In pcregrep, when --colour was used with -o, the list of matching strings
639        was not coloured; this is different to GNU grep, so I have changed it to be
640        the same.
642    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
643        each matching line was coloured. Now it goes on to look for further matches
644        of any of the test patterns, which is the same behaviour as GNU grep.
646    7.  A pattern that could match an empty string could cause pcregrep to loop; it
647        doesn't make sense to accept an empty string match in pcregrep, so I have
648        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
649        seems to be how GNU grep behaves.
651    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
652        start or after a newline", because the conditional assertion was not being
653        correctly handled. The rule now is that both the assertion and what follows
654        in the first alternative must satisfy the test.
656    9.  If auto-callout was enabled in a pattern with a conditional group whose
657        condition was an assertion, PCRE could crash during matching, both with
658        pcre_exec() and pcre_dfa_exec().
660    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
661        used for matching.
663    11. Unicode property support in character classes was not working for
664        characters (bytes) greater than 127 when not in UTF-8 mode.
666    12. Added the -M command line option to pcretest.
668    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
670    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
672    16. Added comments and documentation about mis-use of no_arg in the C++
673        wrapper.
675    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
676        from Martin Jerabek that uses macro names for all relevant character and
677        string constants.
679    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
680        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
681        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
682        these, but not everybody uses configure.
684    19. A conditional group that had only one branch was not being correctly
685        recognized as an item that could match an empty string. This meant that an
686        enclosing group might also not be so recognized, causing infinite looping
687        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
688        with the subject "ab", where knowledge that the repeated group can match
689        nothing is needed in order to break the loop.
691    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
692        exec(), but without supplying a callout function, matching went wrong.
694    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
695        leak if the size of the offset vector was greater than 30. When the vector
696        is smaller, the saved offsets during recursion go onto a local stack
697        vector, but for larger vectors malloc() is used. It was failing to free
698        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
699        error, in fact).
701    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
702        heapframe that is used only when UTF-8 support is enabled. This caused no
703        problem, but was untidy.
705    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
706        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
707        included within another project.
709    24. Steven Van Ingelgem's patches to add more options to the CMake support,
710        slightly modified by me:
712          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
713              not building pcregrep.
715          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
716              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
718    25. Forward references, both numeric and by name, in patterns that made use of
719        duplicate group numbers, could behave incorrectly or give incorrect errors,
720        because when scanning forward to find the reference group, PCRE was not
721        taking into account the duplicate group numbers. A pattern such as
722        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
724    26. Changed a few more instances of "const unsigned char *" to USPTR, making
725        the feature of a custom pointer more persuasive (as requested by a user).
727    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
728        pcretest.c, inside #ifndefs, because it seems they are sometimes already
729        pre-defined.
731    28. Added support for (*UTF8) at the start of a pattern.
733    29. Arrange for flags added by the "release type" setting in CMake to be shown
734        in the configuration summary.
737    Version 7.8 05-Sep-08
738    ---------------------
740    1.  Replaced UCP searching code with optimized version as implemented for Ad
741        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
742        stage table and inline lookup instead of a function, giving speed ups of 2
743        to 5 times on some simple patterns that I tested. Permission was given to
744        distribute the MultiStage2.py script that generates the tables (it's not in
745        the tarball, but is in the Subversion repository).
747    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
748        scripts.
750    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
751        a group with a zero qualifier. The result of the study could be incorrect,
752        or the function might crash, depending on the pattern.
754    4.  Caseless matching was not working for non-ASCII characters in back
755        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
756        It now works when Unicode Property Support is available.
758    5.  In pcretest, an escape such as \x{de} in the data was always generating
759        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
760        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
761        truncation.
763    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
765    7.  Added two (int) casts to pcregrep when printing the difference of two
766        pointers, in case they are 64-bit values.
768    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
769        test 2 if it fails.
771    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
772        and a #define of that name to empty if it is not externally set. This is to
773        allow users of MSVC to set it if necessary.
775    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
776        the convenience functions in the pcre_get.c source file.
778    11. An option change at the start of a pattern that had top-level alternatives
779        could cause overwriting and/or a crash. This command provoked a crash in
780        some environments:
782          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
784        This potential security problem was recorded as CVE-2008-2371.
786    12. For a pattern where the match had to start at the beginning or immediately
787        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
788        pcre_dfa_exec() could read past the end of the passed subject if there was
789        no match. To help with detecting such bugs (e.g. with valgrind), I modified
790        pcretest so that it places the subject at the end of its malloc-ed buffer.
792    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
793        exec() might read past the end of the data buffer in UTF-8 mode.
795    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
796        the data contained the byte 0x85 as part of a UTF-8 character within its
797        first line. This applied both to normal and DFA matching.
799    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
800        /^[^d]*?$/8 failed to match "abc".
802    16. Added a missing copyright notice to pcrecpp_internal.h.
804    17. Make it more clear in the documentation that values returned from
805        pcre_exec() in ovector are byte offsets, not character counts.
807    18. Tidied a few places to stop certain compilers from issuing warnings.
809    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
810        supplied by Stefan Weber. I made a further small update for 7.8 because
811        there is a change of source arrangements: the pcre_searchfuncs.c module is
812        replaced by pcre_ucd.c.
815    Version 7.7 07-May-08
816    ---------------------
818    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
819        a string to a long long, pretend we don't even have a long long." This is
820        done by checking for the strtoq, strtoll, and _strtoi64 functions.
822    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
823        pre-7.6 versions, which defined a global no_arg variable instead of putting
824        it in the RE class. (See also #8 below.)
826    3.  Remove a line of dead code, identified by coverity and reported by Nuno
827        Lopes.
829    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
831        (1) The include/exclude patterns were being applied to the whole pathnames
832            of files, instead of just to the final components.
834        (2) If there was more than one level of directory, the subdirectories were
835            skipped unless they satisfied the include/exclude conditions. This is
836            inconsistent with GNU grep (and could even be seen as contrary to the
837            pcregrep specification - which I improved to make it absolutely clear).
838            The action now is always to scan all levels of directory, and just
839            apply the include/exclude patterns to regular files.
841    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
842        --exclude_dir in the tests to avoid scanning .svn directories.
844    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
845        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
846        doesn't support NULs in patterns.
848    7.  Added some missing "const"s to declarations of static tables in
849        pcre_compile.c and pcre_dfa_exec.c.
851    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
852        caused by fix #2  above. (Subsequently also a second patch to fix the
853        first patch. And a third patch - this was a messy problem.)
855    9.  Applied Craig's patch to remove the use of push_back().
857    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
858        matching function regexec().
860    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
861        which, however, unlike Perl's \g{...}, are subroutine calls, not back
862        references. PCRE supports relative numbers with this syntax (I don't think
863        Oniguruma does).
865    12. Previously, a group with a zero repeat such as (...){0} was completely
866        omitted from the compiled regex. However, this means that if the group
867        was called as a subroutine from elsewhere in the pattern, things went wrong
868        (an internal error was given). Such groups are now left in the compiled
869        pattern, with a new opcode that causes them to be skipped at execution
870        time.
872    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
873        to the way PCRE behaves:
875        (a) A lone ] character is dis-allowed (Perl treats it as data).
877        (b) A back reference to an unmatched subpattern matches an empty string
878            (Perl fails the current match path).
880        (c) A data ] in a character class must be notated as \] because if the
881            first data character in a class is ], it defines an empty class. (In
882            Perl it is not possible to have an empty class.) The empty class []
883            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
884            The negative empty class [^] matches any one character, independently
885            of the DOTALL setting.
887    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
888        non-existent subpattern following a character class starting with ']' and
889        containing () gave an internal compiling error instead of "reference to
890        non-existent subpattern". Fortunately, when the pattern did exist, the
891        compiled code was correct. (When scanning forwards to check for the
892        existencd of the subpattern, it was treating the data ']' as terminating
893        the class, so got the count wrong. When actually compiling, the reference
894        was subsequently set up correctly.)
896    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
897        it was being rejected as not supported by pcre_dfa_exec(), even though
898        other assertions are supported. I have made pcre_dfa_exec() support
899        (*FAIL).
901    16. The implementation of 13c above involved the invention of a new opcode,
902        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
903        cannot be changed at match time, I realized I could make a small
904        improvement to matching performance by compiling OP_ALLANY instead of
905        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
906        on the OP_ANY path.
908    17. Compiling pcretest on Windows with readline support failed without the
909        following two fixes: (1) Make the unistd.h include conditional on
910        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
912    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
913        ncurses library to be included for pcretest when ReadLine support is
914        requested, but also to allow for it to be overridden. This patch came from
915        Daniel Bergström.
917    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
918        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
919        any errors with the current Unicode tables. Thanks to Peter Kankowski for
920        spotting this.
923  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
924  ---------------------  ---------------------

Removed from v.319  
changed lines
  Added in v.587

  ViewVC Help
Powered by ViewVC 1.1.5