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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.277  
changed lines
  Added in v.521

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12