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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.340  
changed lines
  Added in v.537

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12