ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.282  
changed lines
  Added in v.499

  ViewVC Help
Powered by ViewVC 1.1.5