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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.212  
changed lines
  Added in v.491

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12