ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.158  
changed lines
  Added in v.476

ViewVC Help
Powered by ViewVC 1.1.12