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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.267  
changed lines
  Added in v.518

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12