ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.377  
changed lines
  Added in v.524

  ViewVC Help
Powered by ViewVC 1.1.5