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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.331  
changed lines
  Added in v.532

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12