ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 400 by ph10, Sat Mar 21 16:59:40 2009 UTC revision 538 by ph10, Wed Jun 9 19:30:57 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.9 xx-xxx-09  Version 8.10 03-Jun-2010
5    ------------------------
7    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
8        THEN.
10    2.  (*ACCEPT) was not working when inside an atomic group.
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.
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.
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.)
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.
29    7.  Minor change to pcretest.c to avoid a compiler warning.
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).
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.
40    10. Added --line-buffered to pcregrep.
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).
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).
54    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
55        possible starting bytes for non-anchored patterns.
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.
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.)
66    16. Added a lot of (int) casts to avoid compiler warnings in systems where
67        size_t is 64-bit (#991).
69    17. Added a check for running out of memory when PCRE is compiled with
70        --disable-stack-for-recursion (#990).
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.
75    19. The default pcre_chartables.c file recognizes only ASCII characters (values
76        less than 128) in its various bitmaps. However, there is a facility for
77        generating tables according to the current locale when PCRE is compiled. It
78        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
79        characters, are recognized by isspace() and therefore were getting set in
80        these tables. This caused a problem in UTF-8 mode when pcre_study() was
81        used to create a list of bytes that can start a match. For \s, it was
82        including 0x85 and 0xa0, which of course cannot start UTF-8 characters. I
83        have changed the code so that only real ASCII characters (less than 128)
84        are set in this case because the \s etc escapes are documented as
85        recognizing only ASCII characters. (When PCRE_UCP is set - see 9 above -
86        the code is different altogether.)
89    Version 8.02 19-Mar-2010
90    ------------------------
92    1.  The Unicode data tables have been updated to Unicode 5.2.0.
94    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
95        configured.
97    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
98        original author of that file, following a query about its status.
100    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
101        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
103    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
104        quantifier applied to a forward-referencing subroutine call, could compile
105        incorrect code or give the error "internal error: previously-checked
106        referenced subpattern not found".
108    6.  Both MS Visual Studio and Symbian OS have problems with initializing
109        variables to point to external functions. For these systems, therefore,
110        pcre_malloc etc. are now initialized to local functions that call the
111        relevant global functions.
113    7.  There were two entries missing in the vectors called coptable and poptable
114        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
115        I've fixed the data, and added a kludgy way of testing at compile time that
116        the lengths are correct (equal to the number of opcodes).
118    8.  Following on from 7, I added a similar kludge to check the length of the
119        eint vector in pcreposix.c.
121    9.  Error texts for pcre_compile() are held as one long string to avoid too
122        much relocation at load time. To find a text, the string is searched,
123        counting zeros. There was no check for running off the end of the string,
124        which could happen if a new error number was added without updating the
125        string.
127    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
129    11. \K was not working if it appeared in an atomic group or in a group that
130        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
131        \K is "not well defined" if used in an assertion. PCRE now accepts it if
132        the assertion is positive, but not if it is negative.
134    12. Change 11 fortuitously reduced the size of the stack frame used in the
135        "match()" function of pcre_exec.c by one pointer. Forthcoming
136        implementation of support for (*MARK) will need an extra pointer on the
137        stack; I have reserved it now, so that the stack frame size does not
138        decrease.
140    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
141        item in branch that calls a recursion is a subroutine call - as in the
142        second branch in the above example - was incorrectly given the compile-
143        time error "recursive call could loop indefinitely" because pcre_compile()
144        was not correctly checking the subroutine for matching a non-empty string.
146    14. The checks for overrunning compiling workspace could trigger after an
147        overrun had occurred. This is a "should never occur" error, but it can be
148        triggered by pathological patterns such as hundreds of nested parentheses.
149        The checks now trigger 100 bytes before the end of the workspace.
151    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
154    Version 8.01 19-Jan-2010
155    ------------------------
157    1.  If a pattern contained a conditional subpattern with only one branch (in
158        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
159        computed the wrong minimum data length (which is of course zero for such
160        subpatterns). This could cause incorrect "no match" results.
162    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
163        the pattern is reset in the first branch, pcre_compile() failed with
164        "internal error: code overflow at offset...". This happened only when
165        the reset was to the original external option setting. (An optimization
166        abstracts leading options settings into an external setting, which was the
167        cause of this.)
169    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
170        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
171        assertion pattern did not match (meaning that the assertion was true), it
172        was incorrectly treated as false if the SKIP had been reached during the
173        matching. This also applied to assertions used as conditions.
175    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
176        assertion subpattern, including such a pattern used as a condition,
177        unpredictable results occurred, instead of the error return
180    5.  The C++ GlobalReplace function was not working like Perl for the special
181        situation when an empty string is matched. It now does the fancy magic
182        stuff that is necessary.
184    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
185        removed. (These were left over from very, very early versions of PCRE.)
187    7.  Some cosmetic changes to the code to make life easier when compiling it
188        as part of something else:
190        (a) Change DEBUG to PCRE_DEBUG.
192        (b) In pcre_compile(), rename the member of the "branch_chain" structure
193            called "current" as "current_branch", to prevent a collision with the
194            Linux macro when compiled as a kernel module.
196        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
197            prevent a collision with the Linux macro when compiled as a kernel
198            module.
200    8.  In pcre_compile() there are some checks for integer overflows that used to
201        cast potentially large values to (double). This has been changed to that
202        when building, a check for int64_t is made, and if it is found, it is used
203        instead, thus avoiding the use of floating point arithmetic. (There is no
204        other use of FP in PCRE.) If int64_t is not found, the fallback is to
205        double.
207    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
208        2005 (difference between two addresses compared to an unsigned value).
210    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
211        custom one, because of the following reported problem in Windows:
213          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
214              under Win32.
215          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
216              therefore missing the function definition.
217          - The compiler thus generates a "C" signature for the test function.
218          - The linker fails to find the "C" function.
219          - PCRE fails to configure if asked to do so against libbz2.
221    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
222        messages were output:
224          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
225          rerunning libtoolize, to keep the correct libtool macros in-tree.
226          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
228        I have done both of these things.
230    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
231        most of the time, it *can* run out if it is given a pattern that contains a
232        runaway infinite recursion. I updated the discussion in the pcrestack man
233        page.
235    13. Now that we have gone to the x.xx style of version numbers, the minor
236        version may start with zero. Using 08 or 09 is a bad idea because users
237        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
238        interpreted as invalid octal numbers. I've updated the previous comment in
239        configure.ac, and also added a check that gives an error if 08 or 09 are
240        used.
242    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
243        causing partial matching to fail when the end of the subject matched \W
244        in a UTF-8 pattern where \W was quantified with a minimum of 3.
246    15. There were some discrepancies between the declarations in pcre_internal.h
247        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
248        their definitions. The declarations used "const uschar *" and the
249        definitions used USPTR. Even though USPTR is normally defined as "const
250        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
251        reported that: "This difference in casting confuses some C++ compilers, for
252        example, SunCC recognizes above declarations as different functions and
253        generates broken code for hbpcre." I have changed the declarations to use
254        USPTR.
256    16. GNU libtool is named differently on some systems. The autogen.sh script now
257        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
258        (FreeBSD).
260    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
261        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
262        comment: "Figure out how to create a longlong from a string: strtoll and
263        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
264        instance, but it only takes 2 args instead of 3!"
266    18. A subtle bug concerned with back references has been fixed by a change of
267        specification, with a corresponding code fix. A pattern such as
268        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
269        refers, was giving matches when it shouldn't. For example, xa=xaaa would
270        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
271        same bug. Such groups have to be quantified to be useful, or contained
272        inside another quantified group. (If there's no repetition, the reference
273        can never match.) The problem arises because, having left the group and
274        moved on to the rest of the pattern, a later failure that backtracks into
275        the group uses the captured value from the final iteration of the group
276        rather than the correct earlier one. I have fixed this in PCRE by forcing
277        any group that contains a reference to itself to be an atomic group; that
278        is, there cannot be any backtracking into it once it has completed. This is
279        similar to recursive and subroutine calls.
282    Version 8.00 19-Oct-09
283    ----------------------
285    1.  The table for translating pcre_compile() error codes into POSIX error codes
286        was out-of-date, and there was no check on the pcre_compile() error code
287        being within the table. This could lead to an OK return being given in
288        error.
290    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
291        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
292        in a Windows environment.
294    3.  The pcregrep --count option prints the count for each file even when it is
295        zero, as does GNU grep. However, pcregrep was also printing all files when
296        --files-with-matches was added. Now, when both options are given, it prints
297        counts only for those files that have at least one match. (GNU grep just
298        prints the file name in this circumstance, but including the count seems
299        more useful - otherwise, why use --count?) Also ensured that the
300        combination -clh just lists non-zero counts, with no names.
302    4.  The long form of the pcregrep -F option was incorrectly implemented as
303        --fixed_strings instead of --fixed-strings. This is an incompatible change,
304        but it seems right to fix it, and I didn't think it was worth preserving
305        the old behaviour.
307    5.  The command line items --regex=pattern and --regexp=pattern were not
308        recognized by pcregrep, which required --regex pattern or --regexp pattern
309        (with a space rather than an '='). The man page documented the '=' forms,
310        which are compatible with GNU grep; these now work.
312    6.  No libpcreposix.pc file was created for pkg-config; there was just
313        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
315    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
316        when UCP support is not needed, by modifying the Python script that
317        generates it from Unicode data files. This should not matter if the module
318        is correctly used as a library, but I received one complaint about 50K of
319        unwanted data. My guess is that the person linked everything into his
320        program rather than using a library. Anyway, it does no harm.
322    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
323        was a minimum greater than 1 for a wide character in a possessive
324        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
325        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
326        character. Chaos in the form of incorrect output or a compiling loop could
327        result.
329    9.  The restrictions on what a pattern can contain when partial matching is
330        requested for pcre_exec() have been removed. All patterns can now be
331        partially matched by this function. In addition, if there are at least two
332        slots in the offset vector, the offset of the earliest inspected character
333        for the match and the offset of the end of the subject are set in them when
334        PCRE_ERROR_PARTIAL is returned.
336    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
337        synonymous with PCRE_PARTIAL, for backwards compatibility, and
338        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
339        and may be more useful for multi-segment matching.
341    11. Partial matching with pcre_exec() is now more intuitive. A partial match
342        used to be given if ever the end of the subject was reached; now it is
343        given only if matching could not proceed because another character was
344        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
345        string "Z", which now yields "no match" instead of "partial match". In the
346        case of pcre_dfa_exec(), "no match" is given if every matching path for the
347        final character ended with (*FAIL).
349    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
350        if the pattern had a "must contain" character that was already found in the
351        earlier partial match, unless partial matching was again requested. For
352        example, with the pattern /dog.(body)?/, the "must contain" character is
353        "g". If the first part-match was for the string "dog", restarting with
354        "sbody" failed. This bug has been fixed.
356    13. The string returned by pcre_dfa_exec() after a partial match has been
357        changed so that it starts at the first inspected character rather than the
358        first character of the match. This makes a difference only if the pattern
359        starts with a lookbehind assertion or \b or \B (\K is not supported by
360        pcre_dfa_exec()). It's an incompatible change, but it makes the two
361        matching functions compatible, and I think it's the right thing to do.
363    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
364        so that the demonstration program is easily available in environments where
365        PCRE has not been installed from source.
367    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
368        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
369        library.
371    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
372        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
373        is not the first non-POSIX option to be added. Clearly some people find
374        these options useful.
376    17. If a caller to the POSIX matching function regexec() passes a non-zero
377        value for nmatch with a NULL value for pmatch, the value of
378        nmatch is forced to zero.
380    18. RunGrepTest did not have a test for the availability of the -u option of
381        the diff command, as RunTest does. It now checks in the same way as
382        RunTest, and also checks for the -b option.
384    19. If an odd number of negated classes containing just a single character
385        interposed, within parentheses, between a forward reference to a named
386        subpattern and the definition of the subpattern, compilation crashed with
387        an internal error, complaining that it could not find the referenced
388        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
389        [The bug was that it was starting one character too far in when skipping
390        over the character class, thus treating the ] as data rather than
391        terminating the class. This meant it could skip too much.]
393    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
394        /g option in pcretest when the pattern contains \K, which makes it possible
395        to have an empty string match not at the start, even when the pattern is
396        anchored. Updated pcretest and pcredemo to use this option.
398    21. If the maximum number of capturing subpatterns in a recursion was greater
399        than the maximum at the outer level, the higher number was returned, but
400        with unset values at the outer level. The correct (outer level) value is
401        now given.
403    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
404        PCRE did not set those parentheses (unlike Perl). I have now found a way to
405        make it do so. The string so far is captured, making this feature
406        compatible with Perl.
408    23. The tests have been re-organized, adding tests 11 and 12, to make it
409        possible to check the Perl 5.10 features against Perl 5.10.
411    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
412        pattern matches a fixed length string. PCRE did not allow this; now it
413        does. Neither allows recursion.
415    25. I finally figured out how to implement a request to provide the minimum
416        length of subject string that was needed in order to match a given pattern.
417        (It was back references and recursion that I had previously got hung up
418        on.) This code has now been added to pcre_study(); it finds a lower bound
419        to the length of subject needed. It is not necessarily the greatest lower
420        bound, but using it to avoid searching strings that are too short does give
421        some useful speed-ups. The value is available to calling programs via
422        pcre_fullinfo().
424    26. While implementing 25, I discovered to my embarrassment that pcretest had
425        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
426        study optimizations had never been tested with that matching function.
427        Oops. What is worse, even when it was passed study data, there was a bug in
428        pcre_dfa_exec() that meant it never actually used it. Double oops. There
429        were also very few tests of studied patterns with pcre_dfa_exec().
431    27. If (?| is used to create subpatterns with duplicate numbers, they are now
432        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
433        on the other side of the coin, they are no longer allowed to have different
434        names, because these cannot be distinguished in PCRE, and this has caused
435        confusion. (This is a difference from Perl.)
437    28. When duplicate subpattern names are present (necessarily with different
438        numbers, as required by 27 above), and a test is made by name in a
439        conditional pattern, either for a subpattern having been matched, or for
440        recursion in such a pattern, all the associated numbered subpatterns are
441        tested, and the overall condition is true if the condition is true for any
442        one of them. This is the way Perl works, and is also more like the way
443        testing by number works.
446    Version 7.9 11-Apr-09
447  ---------------------  ---------------------
449  1.  When building with support for bzlib/zlib (pcregrep) and/or readline  1.  When building with support for bzlib/zlib (pcregrep) and/or readline
# Line 17  Version 7.9 xx-xxx-09 Line 459  Version 7.9 xx-xxx-09
459      but BOOL is not.      but BOOL is not.
461  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and  3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
462      PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.      PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
464  4.  The pcregrep documentation said spaces were inserted as well as colons (or  4.  The pcregrep documentation said spaces were inserted as well as colons (or
465      hyphens) following file names and line numbers when outputting matching      hyphens) following file names and line numbers when outputting matching
# Line 42  Version 7.9 xx-xxx-09 Line 484  Version 7.9 xx-xxx-09
484      correctly handled. The rule now is that both the assertion and what follows      correctly handled. The rule now is that both the assertion and what follows
485      in the first alternative must satisfy the test.      in the first alternative must satisfy the test.
487  9.  If auto-callout was enabled in a pattern with a conditional group whose  9.  If auto-callout was enabled in a pattern with a conditional group whose
488      condition was an assertion, PCRE could crash during matching, both with      condition was an assertion, PCRE could crash during matching, both with
489      pcre_exec() and pcre_dfa_exec().      pcre_exec() and pcre_dfa_exec().
# Line 64  Version 7.9 xx-xxx-09 Line 506  Version 7.9 xx-xxx-09
506  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch  17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
507      from Martin Jerabek that uses macro names for all relevant character and      from Martin Jerabek that uses macro names for all relevant character and
508      string constants.      string constants.
510  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and  18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
511      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without      SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
512      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of      SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
513      these, but not everybody uses configure.      these, but not everybody uses configure.
515  19. A conditional group that had only one branch was not being correctly  19. A conditional group that had only one branch was not being correctly
516      recognized as an item that could match an empty string. This meant that an      recognized as an item that could match an empty string. This meant that an
517      enclosing group might also not be so recognized, causing infinite looping      enclosing group might also not be so recognized, causing infinite looping
518      (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$      (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
519      with the subject "ab", where knowledge that the repeated group can match      with the subject "ab", where knowledge that the repeated group can match
520      nothing is needed in order to break the loop.      nothing is needed in order to break the loop.
522  20. If a pattern that was compiled with callouts was matched using pcre_dfa_  20. If a pattern that was compiled with callouts was matched using pcre_dfa_
523      exec(), but without supplying a callout function, matching went wrong.      exec(), but without supplying a callout function, matching went wrong.
525  21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory  21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
526      leak if the size of the offset vector was greater than 30. When the vector      leak if the size of the offset vector was greater than 30. When the vector
527      is smaller, the saved offsets during recursion go onto a local stack      is smaller, the saved offsets during recursion go onto a local stack
528      vector, but for larger vectors malloc() is used. It was failing to free      vector, but for larger vectors malloc() is used. It was failing to free
529      when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"      when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
530      error, in fact).      error, in fact).
532    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
533        heapframe that is used only when UTF-8 support is enabled. This caused no
534        problem, but was untidy.
536    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
537        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
538        included within another project.
540    24. Steven Van Ingelgem's patches to add more options to the CMake support,
541        slightly modified by me:
543          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
544              not building pcregrep.
546          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
547              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
549    25. Forward references, both numeric and by name, in patterns that made use of
550        duplicate group numbers, could behave incorrectly or give incorrect errors,
551        because when scanning forward to find the reference group, PCRE was not
552        taking into account the duplicate group numbers. A pattern such as
553        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
555    26. Changed a few more instances of "const unsigned char *" to USPTR, making
556        the feature of a custom pointer more persuasive (as requested by a user).
558    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
559        pcretest.c, inside #ifndefs, because it seems they are sometimes already
560        pre-defined.
562    28. Added support for (*UTF8) at the start of a pattern.
564    29. Arrange for flags added by the "release type" setting in CMake to be shown
565        in the configuration summary.
568  Version 7.8 05-Sep-08  Version 7.8 05-Sep-08
569  ---------------------  ---------------------

Removed from v.400  
changed lines
  Added in v.538

  ViewVC Help
Powered by ViewVC 1.1.5