/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 202 by ph10, Fri Aug 3 09:44:26 2007 UTC revision 584 by ph10, Wed Jan 12 11:41:55 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 05-Jul-07  Version 8.12 12-Jan-2011
5    ------------------------
6    
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.
9    
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.)
14    
15    
16    Version 8.11 10-Dec-2010
17    ------------------------
18    
19    1.  (*THEN) was not working properly if there were untried alternatives prior
20        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
21        backtracked to try for "b" instead of moving to the next alternative branch
22        at the same level (in this case, to look for "c"). The Perl documentation
23        is clear that when (*THEN) is backtracked onto, it goes to the "next
24        alternative in the innermost enclosing group".
25    
26    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
27        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
28        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
29        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
30        (*THEN).
31    
32    3.  If \s appeared in a character class, it removed the VT character from
33        the class, even if it had been included by some previous item, for example
34        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
35        of \s, but is part of the POSIX "space" class.)
36    
37    4.  A partial match never returns an empty string (because you can always
38        match an empty string at the end of the subject); however the checking for
39        an empty string was starting at the "start of match" point. This has been
40        changed to the "earliest inspected character" point, because the returned
41        data for a partial match starts at this character. This means that, for
42        example, /(?<=abc)def/ gives a partial match for the subject "abc"
43        (previously it gave "no match").
44    
45    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
46        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
47        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
48        has an implication that the given string is incomplete (because a partial
49        match is preferred over a full match). For this reason, these items now
50        give a partial match in this situation. [Aside: previously, the one case
51        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
52        match rather than a full match, which was wrong by the old rules, but is
53        now correct.]
54    
55    6.  There was a bug in the handling of #-introduced comments, recognized when
56        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
57        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
58        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
59        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
60        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
61        places in pcre_compile().
62    
63    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
64        comments when looking ahead for named forward references to subpatterns,
65        the only newline sequence it recognized was NL. It now handles newlines
66        according to the set newline convention.
67    
68    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
69        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
70        cater for a lack of strerror(). These oversights have been fixed.
71    
72    9.  Added --match-limit and --recursion-limit to pcregrep.
73    
74    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
75    
76    11. When the -o option was used, pcregrep was setting a return code of 1, even
77        when matches were found, and --line-buffered was not being honoured.
78    
79    12. Added an optional parentheses number to the -o and --only-matching options
80        of pcregrep.
81    
82    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
83        can match an empty string. The code to do it in pcretest and pcredemo
84        needed fixing:
85    
86        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
87            only one byte after an empty string match just before CRLF (this case
88            just got forgotten; "any" and "anycrlf" were OK).
89    
90        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
91            mode when an empty string match preceded an ASCII character followed by
92            a non-ASCII character. (The code for advancing by one character rather
93            than one byte was nonsense.)
94    
95        (c) The pcredemo.c sample program did not have any code at all to handle
96            the cases when CRLF is a valid newline sequence.
97    
98    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
99        as a starting offset was within the subject string. There is now a new
100        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
101        negative or greater than the length of the string. In order to test this,
102        pcretest is extended to allow the setting of negative starting offsets.
103    
104    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
105        starting offset points to the beginning of a UTF-8 character was
106        unnecessarily clumsy. I tidied it up.
107    
108    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
109        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
110    
111    17. Nobody had reported that the --include_dir option, which was added in
112        release 7.7 should have been called --include-dir (hyphen, not underscore)
113        for compatibility with GNU grep. I have changed it to --include-dir, but
114        left --include_dir as an undocumented synonym, and the same for
115        --exclude-dir, though that is not available in GNU grep, at least as of
116        release 2.5.4.
117    
118    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
119        characters from a string of bytes) have been redefined so as not to use
120        loops, in order to improve performance in some environments. At the same
121        time, I abstracted some of the common code into auxiliary macros to save
122        repetition (this should not affect the compiled code).
123    
124    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
125        compile-time error is now given if \c is not followed by an ASCII
126        character, that is, a byte less than 128. (In EBCDIC mode, the code is
127        different, and any byte value is allowed.)
128    
129    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
130        START_OPTIMIZE option, which is now allowed at compile time - but just
131        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
132        to pcregrep and other applications that have no direct access to PCRE
133        options. The new /Y option in pcretest sets this option when calling
134        pcre_compile().
135    
136    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
137        back references. Groups containing recursive back references were forced to
138        be atomic by that change, but in the case of named groups, the amount of
139        memory required was incorrectly computed, leading to "Failed: internal
140        error: code overflow". This has been fixed.
141    
142    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
143        pcretest.c, to avoid build problems in some Borland environments.
144    
145    
146    Version 8.10 25-Jun-2010
147    ------------------------
148    
149    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
150        THEN.
151    
152    2.  (*ACCEPT) was not working when inside an atomic group.
153    
154    3.  Inside a character class, \B is treated as a literal by default, but
155        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
156        causes the error). The code is unchanged, but I tidied the documentation.
157    
158    4.  Inside a character class, PCRE always treated \R and \X as literals,
159        whereas Perl faults them if its -w option is set. I have changed PCRE so
160        that it faults them when PCRE_EXTRA is set.
161    
162    5.  Added support for \N, which always matches any character other than
163        newline. (It is the same as "." when PCRE_DOTALL is not set.)
164    
165    6.  When compiling pcregrep with newer versions of gcc which may have
166        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
167        declared with attribute warn_unused_result" were given. Just casting the
168        result to (void) does not stop the warnings; a more elaborate fudge is
169        needed. I've used a macro to implement this.
170    
171    7.  Minor change to pcretest.c to avoid a compiler warning.
172    
173    8.  Added four artifical Unicode properties to help with an option to make
174        \s etc use properties (see next item). The new properties are: Xan
175        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
176    
177    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
178        use Unicode properties. (*UCP) at the start of a pattern can be used to set
179        this option. Modified pcretest to add /W to test this facility. Added
180        REG_UCP to make it available via the POSIX interface.
181    
182    10. Added --line-buffered to pcregrep.
183    
184    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
185        studied, and the match started with a letter with a code point greater than
186        127 whose first byte was different to the first byte of the other case of
187        the letter, the other case of this starting letter was not recognized
188        (#976).
189    
190    12. If a pattern that was studied started with a repeated Unicode property
191        test, for example, \p{Nd}+, there was the theoretical possibility of
192        setting up an incorrect bitmap of starting bytes, but fortunately it could
193        not have actually happened in practice until change 8 above was made (it
194        added property types that matched character-matching opcodes).
195    
196    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
197        possible starting bytes for non-anchored patterns.
198    
199    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
200        \R, and also a number of cases that involve Unicode properties, both
201        explicit and implicit when PCRE_UCP is set.
202    
203    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
204        input, it could crash or give wrong results if characters with values
205        greater than 0xc0 were present in the subject string. (Detail: it assumed
206        UTF-8 input when processing these items.)
207    
208    16. Added a lot of (int) casts to avoid compiler warnings in systems where
209        size_t is 64-bit (#991).
210    
211    17. Added a check for running out of memory when PCRE is compiled with
212        --disable-stack-for-recursion (#990).
213    
214    18. If the last data line in a file for pcretest does not have a newline on
215        the end, a newline was missing in the output.
216    
217    19. The default pcre_chartables.c file recognizes only ASCII characters (values
218        less than 128) in its various bitmaps. However, there is a facility for
219        generating tables according to the current locale when PCRE is compiled. It
220        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
221        characters, are recognized by isspace() and therefore were getting set in
222        these tables, and indeed these tables seem to approximate to ISO 8859. This
223        caused a problem in UTF-8 mode when pcre_study() was used to create a list
224        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
225        which of course cannot start UTF-8 characters. I have changed the code so
226        that only real ASCII characters (less than 128) and the correct starting
227        bytes for UTF-8 encodings are set for characters greater than 127 when in
228        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
229        altogether.)
230    
231    20. Added the /T option to pcretest so as to be able to run tests with non-
232        standard character tables, thus making it possible to include the tests
233        used for 19 above in the standard set of tests.
234    
235    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
236        reference to a subpattern the other side of a comment that contains an
237        opening parenthesis caused either an internal compiling error, or a
238        reference to the wrong subpattern.
239    
240    
241    Version 8.02 19-Mar-2010
242    ------------------------
243    
244    1.  The Unicode data tables have been updated to Unicode 5.2.0.
245    
246    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
247        configured.
248    
249    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
250        original author of that file, following a query about its status.
251    
252    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
253        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
254    
255    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
256        quantifier applied to a forward-referencing subroutine call, could compile
257        incorrect code or give the error "internal error: previously-checked
258        referenced subpattern not found".
259    
260    6.  Both MS Visual Studio and Symbian OS have problems with initializing
261        variables to point to external functions. For these systems, therefore,
262        pcre_malloc etc. are now initialized to local functions that call the
263        relevant global functions.
264    
265    7.  There were two entries missing in the vectors called coptable and poptable
266        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
267        I've fixed the data, and added a kludgy way of testing at compile time that
268        the lengths are correct (equal to the number of opcodes).
269    
270    8.  Following on from 7, I added a similar kludge to check the length of the
271        eint vector in pcreposix.c.
272    
273    9.  Error texts for pcre_compile() are held as one long string to avoid too
274        much relocation at load time. To find a text, the string is searched,
275        counting zeros. There was no check for running off the end of the string,
276        which could happen if a new error number was added without updating the
277        string.
278    
279    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
280    
281    11. \K was not working if it appeared in an atomic group or in a group that
282        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
283        \K is "not well defined" if used in an assertion. PCRE now accepts it if
284        the assertion is positive, but not if it is negative.
285    
286    12. Change 11 fortuitously reduced the size of the stack frame used in the
287        "match()" function of pcre_exec.c by one pointer. Forthcoming
288        implementation of support for (*MARK) will need an extra pointer on the
289        stack; I have reserved it now, so that the stack frame size does not
290        decrease.
291    
292    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
293        item in branch that calls a recursion is a subroutine call - as in the
294        second branch in the above example - was incorrectly given the compile-
295        time error "recursive call could loop indefinitely" because pcre_compile()
296        was not correctly checking the subroutine for matching a non-empty string.
297    
298    14. The checks for overrunning compiling workspace could trigger after an
299        overrun had occurred. This is a "should never occur" error, but it can be
300        triggered by pathological patterns such as hundreds of nested parentheses.
301        The checks now trigger 100 bytes before the end of the workspace.
302    
303    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
304    
305    
306    Version 8.01 19-Jan-2010
307    ------------------------
308    
309    1.  If a pattern contained a conditional subpattern with only one branch (in
310        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
311        computed the wrong minimum data length (which is of course zero for such
312        subpatterns). This could cause incorrect "no match" results.
313    
314    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
315        the pattern is reset in the first branch, pcre_compile() failed with
316        "internal error: code overflow at offset...". This happened only when
317        the reset was to the original external option setting. (An optimization
318        abstracts leading options settings into an external setting, which was the
319        cause of this.)
320    
321    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
322        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
323        assertion pattern did not match (meaning that the assertion was true), it
324        was incorrectly treated as false if the SKIP had been reached during the
325        matching. This also applied to assertions used as conditions.
326    
327    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
328        assertion subpattern, including such a pattern used as a condition,
329        unpredictable results occurred, instead of the error return
330        PCRE_ERROR_DFA_UITEM.
331    
332    5.  The C++ GlobalReplace function was not working like Perl for the special
333        situation when an empty string is matched. It now does the fancy magic
334        stuff that is necessary.
335    
336    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
337        removed. (These were left over from very, very early versions of PCRE.)
338    
339    7.  Some cosmetic changes to the code to make life easier when compiling it
340        as part of something else:
341    
342        (a) Change DEBUG to PCRE_DEBUG.
343    
344        (b) In pcre_compile(), rename the member of the "branch_chain" structure
345            called "current" as "current_branch", to prevent a collision with the
346            Linux macro when compiled as a kernel module.
347    
348        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
349            prevent a collision with the Linux macro when compiled as a kernel
350            module.
351    
352    8.  In pcre_compile() there are some checks for integer overflows that used to
353        cast potentially large values to (double). This has been changed to that
354        when building, a check for int64_t is made, and if it is found, it is used
355        instead, thus avoiding the use of floating point arithmetic. (There is no
356        other use of FP in PCRE.) If int64_t is not found, the fallback is to
357        double.
358    
359    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
360        2005 (difference between two addresses compared to an unsigned value).
361    
362    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
363        custom one, because of the following reported problem in Windows:
364    
365          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
366              under Win32.
367          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
368              therefore missing the function definition.
369          - The compiler thus generates a "C" signature for the test function.
370          - The linker fails to find the "C" function.
371          - PCRE fails to configure if asked to do so against libbz2.
372    
373    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
374        messages were output:
375    
376          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
377          rerunning libtoolize, to keep the correct libtool macros in-tree.
378          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
379    
380        I have done both of these things.
381    
382    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
383        most of the time, it *can* run out if it is given a pattern that contains a
384        runaway infinite recursion. I updated the discussion in the pcrestack man
385        page.
386    
387    13. Now that we have gone to the x.xx style of version numbers, the minor
388        version may start with zero. Using 08 or 09 is a bad idea because users
389        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
390        interpreted as invalid octal numbers. I've updated the previous comment in
391        configure.ac, and also added a check that gives an error if 08 or 09 are
392        used.
393    
394    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
395        causing partial matching to fail when the end of the subject matched \W
396        in a UTF-8 pattern where \W was quantified with a minimum of 3.
397    
398    15. There were some discrepancies between the declarations in pcre_internal.h
399        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
400        their definitions. The declarations used "const uschar *" and the
401        definitions used USPTR. Even though USPTR is normally defined as "const
402        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
403        reported that: "This difference in casting confuses some C++ compilers, for
404        example, SunCC recognizes above declarations as different functions and
405        generates broken code for hbpcre." I have changed the declarations to use
406        USPTR.
407    
408    16. GNU libtool is named differently on some systems. The autogen.sh script now
409        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
410        (FreeBSD).
411    
412    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
413        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
414        comment: "Figure out how to create a longlong from a string: strtoll and
415        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
416        instance, but it only takes 2 args instead of 3!"
417    
418    18. A subtle bug concerned with back references has been fixed by a change of
419        specification, with a corresponding code fix. A pattern such as
420        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
421        refers, was giving matches when it shouldn't. For example, xa=xaaa would
422        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
423        same bug. Such groups have to be quantified to be useful, or contained
424        inside another quantified group. (If there's no repetition, the reference
425        can never match.) The problem arises because, having left the group and
426        moved on to the rest of the pattern, a later failure that backtracks into
427        the group uses the captured value from the final iteration of the group
428        rather than the correct earlier one. I have fixed this in PCRE by forcing
429        any group that contains a reference to itself to be an atomic group; that
430        is, there cannot be any backtracking into it once it has completed. This is
431        similar to recursive and subroutine calls.
432    
433    
434    Version 8.00 19-Oct-09
435    ----------------------
436    
437    1.  The table for translating pcre_compile() error codes into POSIX error codes
438        was out-of-date, and there was no check on the pcre_compile() error code
439        being within the table. This could lead to an OK return being given in
440        error.
441    
442    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
443        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
444        in a Windows environment.
445    
446    3.  The pcregrep --count option prints the count for each file even when it is
447        zero, as does GNU grep. However, pcregrep was also printing all files when
448        --files-with-matches was added. Now, when both options are given, it prints
449        counts only for those files that have at least one match. (GNU grep just
450        prints the file name in this circumstance, but including the count seems
451        more useful - otherwise, why use --count?) Also ensured that the
452        combination -clh just lists non-zero counts, with no names.
453    
454    4.  The long form of the pcregrep -F option was incorrectly implemented as
455        --fixed_strings instead of --fixed-strings. This is an incompatible change,
456        but it seems right to fix it, and I didn't think it was worth preserving
457        the old behaviour.
458    
459    5.  The command line items --regex=pattern and --regexp=pattern were not
460        recognized by pcregrep, which required --regex pattern or --regexp pattern
461        (with a space rather than an '='). The man page documented the '=' forms,
462        which are compatible with GNU grep; these now work.
463    
464    6.  No libpcreposix.pc file was created for pkg-config; there was just
465        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
466    
467    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
468        when UCP support is not needed, by modifying the Python script that
469        generates it from Unicode data files. This should not matter if the module
470        is correctly used as a library, but I received one complaint about 50K of
471        unwanted data. My guess is that the person linked everything into his
472        program rather than using a library. Anyway, it does no harm.
473    
474    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
475        was a minimum greater than 1 for a wide character in a possessive
476        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
477        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
478        character. Chaos in the form of incorrect output or a compiling loop could
479        result.
480    
481    9.  The restrictions on what a pattern can contain when partial matching is
482        requested for pcre_exec() have been removed. All patterns can now be
483        partially matched by this function. In addition, if there are at least two
484        slots in the offset vector, the offset of the earliest inspected character
485        for the match and the offset of the end of the subject are set in them when
486        PCRE_ERROR_PARTIAL is returned.
487    
488    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
489        synonymous with PCRE_PARTIAL, for backwards compatibility, and
490        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
491        and may be more useful for multi-segment matching.
492    
493    11. Partial matching with pcre_exec() is now more intuitive. A partial match
494        used to be given if ever the end of the subject was reached; now it is
495        given only if matching could not proceed because another character was
496        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
497        string "Z", which now yields "no match" instead of "partial match". In the
498        case of pcre_dfa_exec(), "no match" is given if every matching path for the
499        final character ended with (*FAIL).
500    
501    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
502        if the pattern had a "must contain" character that was already found in the
503        earlier partial match, unless partial matching was again requested. For
504        example, with the pattern /dog.(body)?/, the "must contain" character is
505        "g". If the first part-match was for the string "dog", restarting with
506        "sbody" failed. This bug has been fixed.
507    
508    13. The string returned by pcre_dfa_exec() after a partial match has been
509        changed so that it starts at the first inspected character rather than the
510        first character of the match. This makes a difference only if the pattern
511        starts with a lookbehind assertion or \b or \B (\K is not supported by
512        pcre_dfa_exec()). It's an incompatible change, but it makes the two
513        matching functions compatible, and I think it's the right thing to do.
514    
515    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
516        so that the demonstration program is easily available in environments where
517        PCRE has not been installed from source.
518    
519    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
520        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
521        library.
522    
523    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
524        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
525        is not the first non-POSIX option to be added. Clearly some people find
526        these options useful.
527    
528    17. If a caller to the POSIX matching function regexec() passes a non-zero
529        value for nmatch with a NULL value for pmatch, the value of
530        nmatch is forced to zero.
531    
532    18. RunGrepTest did not have a test for the availability of the -u option of
533        the diff command, as RunTest does. It now checks in the same way as
534        RunTest, and also checks for the -b option.
535    
536    19. If an odd number of negated classes containing just a single character
537        interposed, within parentheses, between a forward reference to a named
538        subpattern and the definition of the subpattern, compilation crashed with
539        an internal error, complaining that it could not find the referenced
540        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
541        [The bug was that it was starting one character too far in when skipping
542        over the character class, thus treating the ] as data rather than
543        terminating the class. This meant it could skip too much.]
544    
545    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
546        /g option in pcretest when the pattern contains \K, which makes it possible
547        to have an empty string match not at the start, even when the pattern is
548        anchored. Updated pcretest and pcredemo to use this option.
549    
550    21. If the maximum number of capturing subpatterns in a recursion was greater
551        than the maximum at the outer level, the higher number was returned, but
552        with unset values at the outer level. The correct (outer level) value is
553        now given.
554    
555    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
556        PCRE did not set those parentheses (unlike Perl). I have now found a way to
557        make it do so. The string so far is captured, making this feature
558        compatible with Perl.
559    
560    23. The tests have been re-organized, adding tests 11 and 12, to make it
561        possible to check the Perl 5.10 features against Perl 5.10.
562    
563    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
564        pattern matches a fixed length string. PCRE did not allow this; now it
565        does. Neither allows recursion.
566    
567    25. I finally figured out how to implement a request to provide the minimum
568        length of subject string that was needed in order to match a given pattern.
569        (It was back references and recursion that I had previously got hung up
570        on.) This code has now been added to pcre_study(); it finds a lower bound
571        to the length of subject needed. It is not necessarily the greatest lower
572        bound, but using it to avoid searching strings that are too short does give
573        some useful speed-ups. The value is available to calling programs via
574        pcre_fullinfo().
575    
576    26. While implementing 25, I discovered to my embarrassment that pcretest had
577        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
578        study optimizations had never been tested with that matching function.
579        Oops. What is worse, even when it was passed study data, there was a bug in
580        pcre_dfa_exec() that meant it never actually used it. Double oops. There
581        were also very few tests of studied patterns with pcre_dfa_exec().
582    
583    27. If (?| is used to create subpatterns with duplicate numbers, they are now
584        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
585        on the other side of the coin, they are no longer allowed to have different
586        names, because these cannot be distinguished in PCRE, and this has caused
587        confusion. (This is a difference from Perl.)
588    
589    28. When duplicate subpattern names are present (necessarily with different
590        numbers, as required by 27 above), and a test is made by name in a
591        conditional pattern, either for a subpattern having been matched, or for
592        recursion in such a pattern, all the associated numbered subpatterns are
593        tested, and the overall condition is true if the condition is true for any
594        one of them. This is the way Perl works, and is also more like the way
595        testing by number works.
596    
597    
598    Version 7.9 11-Apr-09
599    ---------------------
600    
601    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
602        (pcretest), all targets were linked against these libraries. This included
603        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
604        libraries. This caused unwanted dependencies to be created. This problem
605        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
606        pcretest is linked with readline.
607    
608    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
609        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
610        moved outside it again, because FALSE and TRUE are already defined in AIX,
611        but BOOL is not.
612    
613    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
614        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
615    
616    4.  The pcregrep documentation said spaces were inserted as well as colons (or
617        hyphens) following file names and line numbers when outputting matching
618        lines. This is not true; no spaces are inserted. I have also clarified the
619        wording for the --colour (or --color) option.
620    
621    5.  In pcregrep, when --colour was used with -o, the list of matching strings
622        was not coloured; this is different to GNU grep, so I have changed it to be
623        the same.
624    
625    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
626        each matching line was coloured. Now it goes on to look for further matches
627        of any of the test patterns, which is the same behaviour as GNU grep.
628    
629    7.  A pattern that could match an empty string could cause pcregrep to loop; it
630        doesn't make sense to accept an empty string match in pcregrep, so I have
631        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
632        seems to be how GNU grep behaves.
633    
634    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
635        start or after a newline", because the conditional assertion was not being
636        correctly handled. The rule now is that both the assertion and what follows
637        in the first alternative must satisfy the test.
638    
639    9.  If auto-callout was enabled in a pattern with a conditional group whose
640        condition was an assertion, PCRE could crash during matching, both with
641        pcre_exec() and pcre_dfa_exec().
642    
643    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
644        used for matching.
645    
646    11. Unicode property support in character classes was not working for
647        characters (bytes) greater than 127 when not in UTF-8 mode.
648    
649    12. Added the -M command line option to pcretest.
650    
651    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
652    
653    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
654    
655    16. Added comments and documentation about mis-use of no_arg in the C++
656        wrapper.
657    
658    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
659        from Martin Jerabek that uses macro names for all relevant character and
660        string constants.
661    
662    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
663        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
664        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
665        these, but not everybody uses configure.
666    
667    19. A conditional group that had only one branch was not being correctly
668        recognized as an item that could match an empty string. This meant that an
669        enclosing group might also not be so recognized, causing infinite looping
670        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
671        with the subject "ab", where knowledge that the repeated group can match
672        nothing is needed in order to break the loop.
673    
674    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
675        exec(), but without supplying a callout function, matching went wrong.
676    
677    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
678        leak if the size of the offset vector was greater than 30. When the vector
679        is smaller, the saved offsets during recursion go onto a local stack
680        vector, but for larger vectors malloc() is used. It was failing to free
681        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
682        error, in fact).
683    
684    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
685        heapframe that is used only when UTF-8 support is enabled. This caused no
686        problem, but was untidy.
687    
688    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
689        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
690        included within another project.
691    
692    24. Steven Van Ingelgem's patches to add more options to the CMake support,
693        slightly modified by me:
694    
695          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
696              not building pcregrep.
697    
698          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
699              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
700    
701    25. Forward references, both numeric and by name, in patterns that made use of
702        duplicate group numbers, could behave incorrectly or give incorrect errors,
703        because when scanning forward to find the reference group, PCRE was not
704        taking into account the duplicate group numbers. A pattern such as
705        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
706    
707    26. Changed a few more instances of "const unsigned char *" to USPTR, making
708        the feature of a custom pointer more persuasive (as requested by a user).
709    
710    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
711        pcretest.c, inside #ifndefs, because it seems they are sometimes already
712        pre-defined.
713    
714    28. Added support for (*UTF8) at the start of a pattern.
715    
716    29. Arrange for flags added by the "release type" setting in CMake to be shown
717        in the configuration summary.
718    
719    
720    Version 7.8 05-Sep-08
721    ---------------------
722    
723    1.  Replaced UCP searching code with optimized version as implemented for Ad
724        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
725        stage table and inline lookup instead of a function, giving speed ups of 2
726        to 5 times on some simple patterns that I tested. Permission was given to
727        distribute the MultiStage2.py script that generates the tables (it's not in
728        the tarball, but is in the Subversion repository).
729    
730    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
731        scripts.
732    
733    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
734        a group with a zero qualifier. The result of the study could be incorrect,
735        or the function might crash, depending on the pattern.
736    
737    4.  Caseless matching was not working for non-ASCII characters in back
738        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
739        It now works when Unicode Property Support is available.
740    
741    5.  In pcretest, an escape such as \x{de} in the data was always generating
742        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
743        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
744        truncation.
745    
746    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
747    
748    7.  Added two (int) casts to pcregrep when printing the difference of two
749        pointers, in case they are 64-bit values.
750    
751    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
752        test 2 if it fails.
753    
754    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
755        and a #define of that name to empty if it is not externally set. This is to
756        allow users of MSVC to set it if necessary.
757    
758    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
759        the convenience functions in the pcre_get.c source file.
760    
761    11. An option change at the start of a pattern that had top-level alternatives
762        could cause overwriting and/or a crash. This command provoked a crash in
763        some environments:
764    
765          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
766    
767        This potential security problem was recorded as CVE-2008-2371.
768    
769    12. For a pattern where the match had to start at the beginning or immediately
770        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
771        pcre_dfa_exec() could read past the end of the passed subject if there was
772        no match. To help with detecting such bugs (e.g. with valgrind), I modified
773        pcretest so that it places the subject at the end of its malloc-ed buffer.
774    
775    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
776        exec() might read past the end of the data buffer in UTF-8 mode.
777    
778    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
779        the data contained the byte 0x85 as part of a UTF-8 character within its
780        first line. This applied both to normal and DFA matching.
781    
782    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
783        /^[^d]*?$/8 failed to match "abc".
784    
785    16. Added a missing copyright notice to pcrecpp_internal.h.
786    
787    17. Make it more clear in the documentation that values returned from
788        pcre_exec() in ovector are byte offsets, not character counts.
789    
790    18. Tidied a few places to stop certain compilers from issuing warnings.
791    
792    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
793        supplied by Stefan Weber. I made a further small update for 7.8 because
794        there is a change of source arrangements: the pcre_searchfuncs.c module is
795        replaced by pcre_ucd.c.
796    
797    
798    Version 7.7 07-May-08
799    ---------------------
800    
801    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
802        a string to a long long, pretend we don't even have a long long." This is
803        done by checking for the strtoq, strtoll, and _strtoi64 functions.
804    
805    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
806        pre-7.6 versions, which defined a global no_arg variable instead of putting
807        it in the RE class. (See also #8 below.)
808    
809    3.  Remove a line of dead code, identified by coverity and reported by Nuno
810        Lopes.
811    
812    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
813    
814        (1) The include/exclude patterns were being applied to the whole pathnames
815            of files, instead of just to the final components.
816    
817        (2) If there was more than one level of directory, the subdirectories were
818            skipped unless they satisfied the include/exclude conditions. This is
819            inconsistent with GNU grep (and could even be seen as contrary to the
820            pcregrep specification - which I improved to make it absolutely clear).
821            The action now is always to scan all levels of directory, and just
822            apply the include/exclude patterns to regular files.
823    
824    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
825        --exclude_dir in the tests to avoid scanning .svn directories.
826    
827    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
828        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
829        doesn't support NULs in patterns.
830    
831    7.  Added some missing "const"s to declarations of static tables in
832        pcre_compile.c and pcre_dfa_exec.c.
833    
834    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
835        caused by fix #2  above. (Subsequently also a second patch to fix the
836        first patch. And a third patch - this was a messy problem.)
837    
838    9.  Applied Craig's patch to remove the use of push_back().
839    
840    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
841        matching function regexec().
842    
843    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
844        which, however, unlike Perl's \g{...}, are subroutine calls, not back
845        references. PCRE supports relative numbers with this syntax (I don't think
846        Oniguruma does).
847    
848    12. Previously, a group with a zero repeat such as (...){0} was completely
849        omitted from the compiled regex. However, this means that if the group
850        was called as a subroutine from elsewhere in the pattern, things went wrong
851        (an internal error was given). Such groups are now left in the compiled
852        pattern, with a new opcode that causes them to be skipped at execution
853        time.
854    
855    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
856        to the way PCRE behaves:
857    
858        (a) A lone ] character is dis-allowed (Perl treats it as data).
859    
860        (b) A back reference to an unmatched subpattern matches an empty string
861            (Perl fails the current match path).
862    
863        (c) A data ] in a character class must be notated as \] because if the
864            first data character in a class is ], it defines an empty class. (In
865            Perl it is not possible to have an empty class.) The empty class []
866            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
867            The negative empty class [^] matches any one character, independently
868            of the DOTALL setting.
869    
870    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
871        non-existent subpattern following a character class starting with ']' and
872        containing () gave an internal compiling error instead of "reference to
873        non-existent subpattern". Fortunately, when the pattern did exist, the
874        compiled code was correct. (When scanning forwards to check for the
875        existencd of the subpattern, it was treating the data ']' as terminating
876        the class, so got the count wrong. When actually compiling, the reference
877        was subsequently set up correctly.)
878    
879    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
880        it was being rejected as not supported by pcre_dfa_exec(), even though
881        other assertions are supported. I have made pcre_dfa_exec() support
882        (*FAIL).
883    
884    16. The implementation of 13c above involved the invention of a new opcode,
885        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
886        cannot be changed at match time, I realized I could make a small
887        improvement to matching performance by compiling OP_ALLANY instead of
888        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
889        on the OP_ANY path.
890    
891    17. Compiling pcretest on Windows with readline support failed without the
892        following two fixes: (1) Make the unistd.h include conditional on
893        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
894    
895    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
896        ncurses library to be included for pcretest when ReadLine support is
897        requested, but also to allow for it to be overridden. This patch came from
898        Daniel Bergström.
899    
900    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
901        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
902        any errors with the current Unicode tables. Thanks to Peter Kankowski for
903        spotting this.
904    
905    
906    Version 7.6 28-Jan-08
907    ---------------------
908    
909    1.  A character class containing a very large number of characters with
910        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
911        overflow.
912    
913    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
914        HAVE_LONG_LONG is not defined.
915    
916    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
917        bring them up to date and include new features. This patch includes:
918    
919        - Fixed PH's badly added libz and libbz2 support.
920        - Fixed a problem with static linking.
921        - Added pcredemo. [But later removed - see 7 below.]
922        - Fixed dftables problem and added an option.
923        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
924            HAVE_LONG_LONG.
925        - Added readline support for pcretest.
926        - Added an listing of the option settings after cmake has run.
927    
928    4.  A user submitted a patch to Makefile that makes it easy to create
929        "pcre.dll" under mingw when using Configure/Make. I added stuff to
930        Makefile.am that cause it to include this special target, without
931        affecting anything else. Note that the same mingw target plus all
932        the other distribution libraries and programs are now supported
933        when configuring with CMake (see 6 below) instead of with
934        Configure/Make.
935    
936    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
937        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
938        exported in the Windows port". It has not yet been confirmed that the patch
939        solves the problem, but it does no harm.
940    
941    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
942        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
943        with CMake, and also correct the comment about stack recursion.
944    
945    7.  Remove the automatic building of pcredemo from the ./configure system and
946        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
947        of a program that users should build themselves after PCRE is installed, so
948        building it automatically is not really right. What is more, it gave
949        trouble in some build environments.
950    
951    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
952    
953    
954    Version 7.5 10-Jan-08
955    ---------------------
956    
957    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
958        values in parens when parsing an RE using the C++ wrapper."
959    
960    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
961        Characters greater than 255 were excluded from the class instead of being
962        included.
963    
964    3.  The same bug as (2) above applied to negated POSIX classes such as
965        [:^space:].
966    
967    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
968        defined or documented. It seems to have been a typo for PCRE_STATIC, so
969        I have changed it.
970    
971    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
972        first named subpattern) and a construct such as (?&a) would reference the
973        first named subpattern whose name started with "a" (in other words, the
974        length check was missing). Both these problems are fixed. "Subpattern name
975        expected" is now given for (?&) (a zero-length name), and this patch also
976        makes it give the same error for \k'' (previously it complained that that
977        was a reference to a non-existent subpattern).
978    
979    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
980        this is right because (?- can be followed by option settings as well as by
981        digits. I have, however, made the messages clearer.
982    
983    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
984        than the number used in the conditional) now cause a compile-time error.
985        This is actually not compatible with Perl, which accepts such patterns, but
986        treats the conditional as always being FALSE (as PCRE used to), but it
987        seems to me that giving a diagnostic is better.
988    
989    8.  Change "alphameric" to the more common word "alphanumeric" in comments
990        and messages.
991    
992    9.  Fix two occurrences of "backslash" in comments that should have been
993        "backspace".
994    
995    10. Remove two redundant lines of code that can never be obeyed (their function
996        was moved elsewhere).
997    
998    11. The program that makes PCRE's Unicode character property table had a bug
999        which caused it to generate incorrect table entries for sequences of
1000        characters that have the same character type, but are in different scripts.
1001        It amalgamated them into a single range, with the script of the first of
1002        them. In other words, some characters were in the wrong script. There were
1003        thirteen such cases, affecting characters in the following ranges:
1004    
1005          U+002b0 - U+002c1
1006          U+0060c - U+0060d
1007          U+0061e - U+00612
1008          U+0064b - U+0065e
1009          U+0074d - U+0076d
1010          U+01800 - U+01805
1011          U+01d00 - U+01d77
1012          U+01d9b - U+01dbf
1013          U+0200b - U+0200f
1014          U+030fc - U+030fe
1015          U+03260 - U+0327f
1016          U+0fb46 - U+0fbb1
1017          U+10450 - U+1049d
1018    
1019    12. The -o option (show only the matching part of a line) for pcregrep was not
1020        compatible with GNU grep in that, if there was more than one match in a
1021        line, it showed only the first of them. It now behaves in the same way as
1022        GNU grep.
1023    
1024    13. If the -o and -v options were combined for pcregrep, it printed a blank
1025        line for every non-matching line. GNU grep prints nothing, and pcregrep now
1026        does the same. The return code can be used to tell if there were any
1027        non-matching lines.
1028    
1029    14. Added --file-offsets and --line-offsets to pcregrep.
1030    
1031    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1032        infinitely looping recursion. The bug was that positive lookaheads were not
1033        being skipped when checking for a possible empty match (negative lookaheads
1034        and both kinds of lookbehind were skipped).
1035    
1036    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1037        inclusion of <windows.h> to before rather than after the definition of
1038        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1039    
1040    17. Specifying a possessive quantifier with a specific limit for a Unicode
1041        character property caused pcre_compile() to compile bad code, which led at
1042        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1043        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1044        caused the error; without that there was no problem.
1045    
1046    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1047    
1048    19. Added --enable-pcretest-libreadline.
1049    
1050    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1051        RE::GlobalReplace(). As a result, the number of replacements returned was
1052        double what it should be. I removed one of the increments, but Craig sent a
1053        later patch that removed the other one (the right fix) and added unit tests
1054        that check the return values (which was not done before).
1055    
1056    21. Several CMake things:
1057    
1058        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1059            the names libpcre and libpcreposix, not just pcre and pcreposix.
1060    
1061        (2) The above change means that pcretest and pcregrep are now correctly
1062            linked with the newly-built libraries, not previously installed ones.
1063    
1064        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
1065    
1066    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1067        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1068        UTF-8 newline character). The key issue is that the pattern starts .*;
1069        this means that the match must be either at the beginning, or after a
1070        newline. The bug was in the code for advancing after a failed match and
1071        checking that the new position followed a newline. It was not taking
1072        account of UTF-8 characters correctly.
1073    
1074    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1075        character classes. PCRE was not treating the sequence [:...:] as a
1076        character class unless the ... were all letters. Perl, however, seems to
1077        allow any characters between [: and :], though of course it rejects as
1078        unknown any "names" that contain non-letters, because all the known class
1079        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1080        for example, whereas PCRE did not - it did not recognize a POSIX character
1081        class. This seemed a bit dangerous, so the code has been changed to be
1082        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1083        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1084        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1085        Perl does, and where it didn't before.
1086    
1087    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1088        Windows environments %n is disabled by default.
1089    
1090    
1091    Version 7.4 21-Sep-07
1092    ---------------------
1093    
1094    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
1095        means that a class such as [\s] counted as "explicit reference to CR or
1096        LF". That isn't really right - the whole point of the change was to try to
1097        help when there was an actual mention of one of the two characters. So now
1098        the change happens only if \r or \n (or a literal CR or LF) character is
1099        encountered.
1100    
1101    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
1102        of both had grown to the point where there were only 3 bits left.
1103        Fortunately, there was spare space in the data structure, and so I have
1104        moved the internal flags into a new 16-bit field to free up more option
1105        bits.
1106    
1107    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
1108        but did not set the internal JCHANGED flag - either of these is enough to
1109        control the way the "get" function works - but the PCRE_INFO_JCHANGED
1110        facility is supposed to tell if (?J) was ever used, so now (?J) at the
1111        start sets both bits.
1112    
1113    4.  Added options (at build time, compile time, exec time) to change \R from
1114        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
1115    
1116    5.  doc/pcresyntax.html was missing from the distribution.
1117    
1118    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
1119        compatibility, even though it is no longer used.
1120    
1121    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
1122        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
1123        windows.h file is present (where different names are used). [This was
1124        reversed later after testing - see 16 below.]
1125    
1126    8.  Changed all #include <config.h> to #include "config.h". There were also
1127        some further <pcre.h> cases that I changed to "pcre.h".
1128    
1129    9.  When pcregrep was used with the --colour option, it missed the line ending
1130        sequence off the lines that it output.
1131    
1132    10. It was pointed out to me that arrays of string pointers cause lots of
1133        relocations when a shared library is dynamically loaded. A technique of
1134        using a single long string with a table of offsets can drastically reduce
1135        these. I have refactored PCRE in four places to do this. The result is
1136        dramatic:
1137    
1138          Originally:                          290
1139          After changing UCP table:            187
1140          After changing error message table:   43
1141          After changing table of "verbs"       36
1142          After changing table of Posix names   22
1143    
1144        Thanks to the folks working on Gregex for glib for this insight.
1145    
1146    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
1147        unicode-properties was also set.
1148    
1149    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
1150    
1151    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
1152        checked only for CRLF.
1153    
1154    14. Added casts to pcretest.c to avoid compiler warnings.
1155    
1156    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
1157    
1158    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
1159        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
1160        entirely. This removes changes made in 7 above.
1161    
1162    17. The CMake files have been updated, and there is now more information about
1163        building with CMake in the NON-UNIX-USE document.
1164    
1165    
1166    Version 7.3 28-Aug-07
1167  ---------------------  ---------------------
1168    
1169   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 65  Version 7.3 05-Jul-07 Line 1227  Version 7.3 05-Jul-07
1227      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
1228      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
1229    
1230    10. Fixed a bug in the documentation for get/copy named substring when
1231        duplicate names are permitted. If none of the named substrings are set, the
1232        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
1233        empty string.
1234    
1235    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
1236        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
1237        because the ] is interpreted as the first data character and the
1238        terminating ] is not found. PCRE has been made compatible with Perl in this
1239        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
1240        cause memory overwriting.
1241    
1242    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
1243        string has been matched (to stop an infinite loop). It was not recognizing
1244        a conditional subpattern that could match an empty string if that
1245        subpattern was within another subpattern. For example, it looped when
1246        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
1247        condition was not nested. This bug has been fixed.
1248    
1249    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
1250        past the start of the subject in the presence of bytes with the top bit
1251        set, for example "\x8aBCD".
1252    
1253    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
1254        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
1255    
1256    14. Optimized (?!) to (*FAIL).
1257    
1258    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
1259        This restricts code points to be within the range 0 to 0x10FFFF, excluding
1260        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
1261        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
1262        does: it's just the validity check that is more restrictive.
1263    
1264    16. Inserted checks for integer overflows during escape sequence (backslash)
1265        processing, and also fixed erroneous offset values for syntax errors during
1266        backslash processing.
1267    
1268    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
1269        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
1270    
1271    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
1272        caused an overrun.
1273    
1274    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
1275        something other than just ASCII characters) inside a group that had an
1276        unlimited repeat caused a loop at compile time (while checking to see
1277        whether the group could match an empty string).
1278    
1279    20. Debugging a pattern containing \p or \P could cause a crash. For example,
1280        [\P{Any}] did so. (Error in the code for printing property names.)
1281    
1282    21. An orphan \E inside a character class could cause a crash.
1283    
1284    22. A repeated capturing bracket such as (A)? could cause a wild memory
1285        reference during compilation.
1286    
1287    23. There are several functions in pcre_compile() that scan along a compiled
1288        expression for various reasons (e.g. to see if it's fixed length for look
1289        behind). There were bugs in these functions when a repeated \p or \P was
1290        present in the pattern. These operators have additional parameters compared
1291        with \d, etc, and these were not being taken into account when moving along
1292        the compiled data. Specifically:
1293    
1294        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
1295            length.
1296    
1297        (b) An item such as \pL+ within a repeated group could cause crashes or
1298            loops.
1299    
1300        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
1301            "reference to non-existent subpattern" error.
1302    
1303        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
1304    
1305    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
1306        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
1307    
1308    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
1309    
1310    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
1311        character were causing crashes (broken optimization).
1312    
1313    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
1314        \p or \P) caused a compile-time loop.
1315    
1316    28. More problems have arisen in unanchored patterns when CRLF is a valid line
1317        break. For example, the unstudied pattern [\r\n]A does not match the string
1318        "\r\nA" because change 7.0/46 below moves the current point on by two
1319        characters after failing to match at the start. However, the pattern \nA
1320        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
1321        the same is true. There doesn't seem any very clean way out of this, but
1322        what I have chosen to do makes the common cases work: PCRE now takes note
1323        of whether there can be an explicit match for \r or \n anywhere in the
1324        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1325        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1326        pattern has explicit CR or LF references.
1327    
1328    29. Added (*CR) etc for changing newline setting at start of pattern.
1329    
1330    
1331  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
1332  ---------------------  ---------------------

Legend:
Removed from v.202  
changed lines
  Added in v.584

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12