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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.270  
changed lines
  Added in v.515

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12