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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.268  
changed lines
  Added in v.516

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12