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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.402  
changed lines
  Added in v.531

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12