ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 200 by ph10, Wed Aug 1 09:10:40 2007 UTC revision 480 by ph10, Sun Jan 3 17:29:59 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-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).
60    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
61        custom one, because of the following reported problem in Windows:
63          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
64            under Win32.
65          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
66            therefore missing the function definition.
67          - The compiler thus generates a "C" signature for the test function.
68          - The linker fails to find the "C" function.
69          - PCRE fails to configure if asked to do so against libbz2.
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
78        I have done both of these things.
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
87    Version 8.00 19-Oct-09
88    ----------------------
90    1.  The table for translating pcre_compile() error codes into POSIX error codes
91        was out-of-date, and there was no check on the pcre_compile() error code
92        being within the table. This could lead to an OK return being given in
93        error.
95    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
96        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
97        in a Windows environment.
99    3.  The pcregrep --count option prints the count for each file even when it is
100        zero, as does GNU grep. However, pcregrep was also printing all files when
101        --files-with-matches was added. Now, when both options are given, it prints
102        counts only for those files that have at least one match. (GNU grep just
103        prints the file name in this circumstance, but including the count seems
104        more useful - otherwise, why use --count?) Also ensured that the
105        combination -clh just lists non-zero counts, with no names.
107    4.  The long form of the pcregrep -F option was incorrectly implemented as
108        --fixed_strings instead of --fixed-strings. This is an incompatible change,
109        but it seems right to fix it, and I didn't think it was worth preserving
110        the old behaviour.
112    5.  The command line items --regex=pattern and --regexp=pattern were not
113        recognized by pcregrep, which required --regex pattern or --regexp pattern
114        (with a space rather than an '='). The man page documented the '=' forms,
115        which are compatible with GNU grep; these now work.
117    6.  No libpcreposix.pc file was created for pkg-config; there was just
118        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
120    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
121        when UCP support is not needed, by modifying the Python script that
122        generates it from Unicode data files. This should not matter if the module
123        is correctly used as a library, but I received one complaint about 50K of
124        unwanted data. My guess is that the person linked everything into his
125        program rather than using a library. Anyway, it does no harm.
127    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
128        was a minimum greater than 1 for a wide character in a possessive
129        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
130        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
131        character. Chaos in the form of incorrect output or a compiling loop could
132        result.
134    9.  The restrictions on what a pattern can contain when partial matching is
135        requested for pcre_exec() have been removed. All patterns can now be
136        partially matched by this function. In addition, if there are at least two
137        slots in the offset vector, the offset of the earliest inspected character
138        for the match and the offset of the end of the subject are set in them when
139        PCRE_ERROR_PARTIAL is returned.
141    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
142        synonymous with PCRE_PARTIAL, for backwards compatibility, and
143        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
144        and may be more useful for multi-segment matching.
146    11. Partial matching with pcre_exec() is now more intuitive. A partial match
147        used to be given if ever the end of the subject was reached; now it is
148        given only if matching could not proceed because another character was
149        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
150        string "Z", which now yields "no match" instead of "partial match". In the
151        case of pcre_dfa_exec(), "no match" is given if every matching path for the
152        final character ended with (*FAIL).
154    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
155        if the pattern had a "must contain" character that was already found in the
156        earlier partial match, unless partial matching was again requested. For
157        example, with the pattern /dog.(body)?/, the "must contain" character is
158        "g". If the first part-match was for the string "dog", restarting with
159        "sbody" failed. This bug has been fixed.
161    13. The string returned by pcre_dfa_exec() after a partial match has been
162        changed so that it starts at the first inspected character rather than the
163        first character of the match. This makes a difference only if the pattern
164        starts with a lookbehind assertion or \b or \B (\K is not supported by
165        pcre_dfa_exec()). It's an incompatible change, but it makes the two
166        matching functions compatible, and I think it's the right thing to do.
168    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
169        so that the demonstration program is easily available in environments where
170        PCRE has not been installed from source.
172    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
173        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
174        library.
176    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
177        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
178        is not the first non-POSIX option to be added. Clearly some people find
179        these options useful.
181    17. If a caller to the POSIX matching function regexec() passes a non-zero
182        value for nmatch with a NULL value for pmatch, the value of
183        nmatch is forced to zero.
185    18. RunGrepTest did not have a test for the availability of the -u option of
186        the diff command, as RunTest does. It now checks in the same way as
187        RunTest, and also checks for the -b option.
189    19. If an odd number of negated classes containing just a single character
190        interposed, within parentheses, between a forward reference to a named
191        subpattern and the definition of the subpattern, compilation crashed with
192        an internal error, complaining that it could not find the referenced
193        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
194        [The bug was that it was starting one character too far in when skipping
195        over the character class, thus treating the ] as data rather than
196        terminating the class. This meant it could skip too much.]
198    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
199        /g option in pcretest when the pattern contains \K, which makes it possible
200        to have an empty string match not at the start, even when the pattern is
201        anchored. Updated pcretest and pcredemo to use this option.
203    21. If the maximum number of capturing subpatterns in a recursion was greater
204        than the maximum at the outer level, the higher number was returned, but
205        with unset values at the outer level. The correct (outer level) value is
206        now given.
208    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
209        PCRE did not set those parentheses (unlike Perl). I have now found a way to
210        make it do so. The string so far is captured, making this feature
211        compatible with Perl.
213    23. The tests have been re-organized, adding tests 11 and 12, to make it
214        possible to check the Perl 5.10 features against Perl 5.10.
216    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
217        pattern matches a fixed length string. PCRE did not allow this; now it
218        does. Neither allows recursion.
220    25. I finally figured out how to implement a request to provide the minimum
221        length of subject string that was needed in order to match a given pattern.
222        (It was back references and recursion that I had previously got hung up
223        on.) This code has now been added to pcre_study(); it finds a lower bound
224        to the length of subject needed. It is not necessarily the greatest lower
225        bound, but using it to avoid searching strings that are too short does give
226        some useful speed-ups. The value is available to calling programs via
227        pcre_fullinfo().
229    26. While implementing 25, I discovered to my embarrassment that pcretest had
230        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
231        study optimizations had never been tested with that matching function.
232        Oops. What is worse, even when it was passed study data, there was a bug in
233        pcre_dfa_exec() that meant it never actually used it. Double oops. There
234        were also very few tests of studied patterns with pcre_dfa_exec().
236    27. If (?| is used to create subpatterns with duplicate numbers, they are now
237        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
238        on the other side of the coin, they are no longer allowed to have different
239        names, because these cannot be distinguished in PCRE, and this has caused
240        confusion. (This is a difference from Perl.)
242    28. When duplicate subpattern names are present (necessarily with different
243        numbers, as required by 27 above), and a test is made by name in a
244        conditional pattern, either for a subpattern having been matched, or for
245        recursion in such a pattern, all the associated numbered subpatterns are
246        tested, and the overall condition is true if the condition is true for any
247        one of them. This is the way Perl works, and is also more like the way
248        testing by number works.
251    Version 7.9 11-Apr-09
252    ---------------------
254    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
255        (pcretest), all targets were linked against these libraries. This included
256        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
257        libraries. This caused unwanted dependencies to be created. This problem
258        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
259        pcretest is linked with readline.
261    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
262        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
263        moved outside it again, because FALSE and TRUE are already defined in AIX,
264        but BOOL is not.
266    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
267        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
269    4.  The pcregrep documentation said spaces were inserted as well as colons (or
270        hyphens) following file names and line numbers when outputting matching
271        lines. This is not true; no spaces are inserted. I have also clarified the
272        wording for the --colour (or --color) option.
274    5.  In pcregrep, when --colour was used with -o, the list of matching strings
275        was not coloured; this is different to GNU grep, so I have changed it to be
276        the same.
278    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
279        each matching line was coloured. Now it goes on to look for further matches
280        of any of the test patterns, which is the same behaviour as GNU grep.
282    7.  A pattern that could match an empty string could cause pcregrep to loop; it
283        doesn't make sense to accept an empty string match in pcregrep, so I have
284        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
285        seems to be how GNU grep behaves.
287    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
288        start or after a newline", because the conditional assertion was not being
289        correctly handled. The rule now is that both the assertion and what follows
290        in the first alternative must satisfy the test.
292    9.  If auto-callout was enabled in a pattern with a conditional group whose
293        condition was an assertion, PCRE could crash during matching, both with
294        pcre_exec() and pcre_dfa_exec().
296    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
297        used for matching.
299    11. Unicode property support in character classes was not working for
300        characters (bytes) greater than 127 when not in UTF-8 mode.
302    12. Added the -M command line option to pcretest.
304    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
306    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
308    16. Added comments and documentation about mis-use of no_arg in the C++
309        wrapper.
311    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
312        from Martin Jerabek that uses macro names for all relevant character and
313        string constants.
315    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
316        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
317        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
318        these, but not everybody uses configure.
320    19. A conditional group that had only one branch was not being correctly
321        recognized as an item that could match an empty string. This meant that an
322        enclosing group might also not be so recognized, causing infinite looping
323        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
324        with the subject "ab", where knowledge that the repeated group can match
325        nothing is needed in order to break the loop.
327    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
328        exec(), but without supplying a callout function, matching went wrong.
330    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
331        leak if the size of the offset vector was greater than 30. When the vector
332        is smaller, the saved offsets during recursion go onto a local stack
333        vector, but for larger vectors malloc() is used. It was failing to free
334        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
335        error, in fact).
337    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
338        heapframe that is used only when UTF-8 support is enabled. This caused no
339        problem, but was untidy.
341    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
342        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
343        included within another project.
345    24. Steven Van Ingelgem's patches to add more options to the CMake support,
346        slightly modified by me:
348          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
349              not building pcregrep.
351          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
352              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
354    25. Forward references, both numeric and by name, in patterns that made use of
355        duplicate group numbers, could behave incorrectly or give incorrect errors,
356        because when scanning forward to find the reference group, PCRE was not
357        taking into account the duplicate group numbers. A pattern such as
358        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
360    26. Changed a few more instances of "const unsigned char *" to USPTR, making
361        the feature of a custom pointer more persuasive (as requested by a user).
363    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
364        pcretest.c, inside #ifndefs, because it seems they are sometimes already
365        pre-defined.
367    28. Added support for (*UTF8) at the start of a pattern.
369    29. Arrange for flags added by the "release type" setting in CMake to be shown
370        in the configuration summary.
373    Version 7.8 05-Sep-08
374    ---------------------
376    1.  Replaced UCP searching code with optimized version as implemented for Ad
377        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
378        stage table and inline lookup instead of a function, giving speed ups of 2
379        to 5 times on some simple patterns that I tested. Permission was given to
380        distribute the MultiStage2.py script that generates the tables (it's not in
381        the tarball, but is in the Subversion repository).
383    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
384        scripts.
386    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
387        a group with a zero qualifier. The result of the study could be incorrect,
388        or the function might crash, depending on the pattern.
390    4.  Caseless matching was not working for non-ASCII characters in back
391        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
392        It now works when Unicode Property Support is available.
394    5.  In pcretest, an escape such as \x{de} in the data was always generating
395        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
396        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
397        truncation.
399    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
401    7.  Added two (int) casts to pcregrep when printing the difference of two
402        pointers, in case they are 64-bit values.
404    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
405        test 2 if it fails.
407    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
408        and a #define of that name to empty if it is not externally set. This is to
409        allow users of MSVC to set it if necessary.
411    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
412        the convenience functions in the pcre_get.c source file.
414    11. An option change at the start of a pattern that had top-level alternatives
415        could cause overwriting and/or a crash. This command provoked a crash in
416        some environments:
418          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
420        This potential security problem was recorded as CVE-2008-2371.
422    12. For a pattern where the match had to start at the beginning or immediately
423        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
424        pcre_dfa_exec() could read past the end of the passed subject if there was
425        no match. To help with detecting such bugs (e.g. with valgrind), I modified
426        pcretest so that it places the subject at the end of its malloc-ed buffer.
428    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
429        exec() might read past the end of the data buffer in UTF-8 mode.
431    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
432        the data contained the byte 0x85 as part of a UTF-8 character within its
433        first line. This applied both to normal and DFA matching.
435    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
436        /^[^d]*?$/8 failed to match "abc".
438    16. Added a missing copyright notice to pcrecpp_internal.h.
440    17. Make it more clear in the documentation that values returned from
441        pcre_exec() in ovector are byte offsets, not character counts.
443    18. Tidied a few places to stop certain compilers from issuing warnings.
445    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
446        supplied by Stefan Weber. I made a further small update for 7.8 because
447        there is a change of source arrangements: the pcre_searchfuncs.c module is
448        replaced by pcre_ucd.c.
451    Version 7.7 07-May-08
452    ---------------------
454    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
455        a string to a long long, pretend we don't even have a long long." This is
456        done by checking for the strtoq, strtoll, and _strtoi64 functions.
458    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
459        pre-7.6 versions, which defined a global no_arg variable instead of putting
460        it in the RE class. (See also #8 below.)
462    3.  Remove a line of dead code, identified by coverity and reported by Nuno
463        Lopes.
465    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
467        (1) The include/exclude patterns were being applied to the whole pathnames
468            of files, instead of just to the final components.
470        (2) If there was more than one level of directory, the subdirectories were
471            skipped unless they satisfied the include/exclude conditions. This is
472            inconsistent with GNU grep (and could even be seen as contrary to the
473            pcregrep specification - which I improved to make it absolutely clear).
474            The action now is always to scan all levels of directory, and just
475            apply the include/exclude patterns to regular files.
477    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
478        --exclude_dir in the tests to avoid scanning .svn directories.
480    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
481        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
482        doesn't support NULs in patterns.
484    7.  Added some missing "const"s to declarations of static tables in
485        pcre_compile.c and pcre_dfa_exec.c.
487    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
488        caused by fix #2  above. (Subsequently also a second patch to fix the
489        first patch. And a third patch - this was a messy problem.)
491    9.  Applied Craig's patch to remove the use of push_back().
493    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
494        matching function regexec().
496    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
497        which, however, unlike Perl's \g{...}, are subroutine calls, not back
498        references. PCRE supports relative numbers with this syntax (I don't think
499        Oniguruma does).
501    12. Previously, a group with a zero repeat such as (...){0} was completely
502        omitted from the compiled regex. However, this means that if the group
503        was called as a subroutine from elsewhere in the pattern, things went wrong
504        (an internal error was given). Such groups are now left in the compiled
505        pattern, with a new opcode that causes them to be skipped at execution
506        time.
508    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
509        to the way PCRE behaves:
511        (a) A lone ] character is dis-allowed (Perl treats it as data).
513        (b) A back reference to an unmatched subpattern matches an empty string
514            (Perl fails the current match path).
516        (c) A data ] in a character class must be notated as \] because if the
517            first data character in a class is ], it defines an empty class. (In
518            Perl it is not possible to have an empty class.) The empty class []
519            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
520            The negative empty class [^] matches any one character, independently
521            of the DOTALL setting.
523    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
524        non-existent subpattern following a character class starting with ']' and
525        containing () gave an internal compiling error instead of "reference to
526        non-existent subpattern". Fortunately, when the pattern did exist, the
527        compiled code was correct. (When scanning forwards to check for the
528        existencd of the subpattern, it was treating the data ']' as terminating
529        the class, so got the count wrong. When actually compiling, the reference
530        was subsequently set up correctly.)
532    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
533        it was being rejected as not supported by pcre_dfa_exec(), even though
534        other assertions are supported. I have made pcre_dfa_exec() support
535        (*FAIL).
537    16. The implementation of 13c above involved the invention of a new opcode,
538        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
539        cannot be changed at match time, I realized I could make a small
540        improvement to matching performance by compiling OP_ALLANY instead of
541        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
542        on the OP_ANY path.
544    17. Compiling pcretest on Windows with readline support failed without the
545        following two fixes: (1) Make the unistd.h include conditional on
546        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
548    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
549        ncurses library to be included for pcretest when ReadLine support is
550        requested, but also to allow for it to be overridden. This patch came from
551        Daniel Bergström.
553    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
554        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
555        any errors with the current Unicode tables. Thanks to Peter Kankowski for
556        spotting this.
559    Version 7.6 28-Jan-08
560    ---------------------
562    1.  A character class containing a very large number of characters with
563        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
564        overflow.
566    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
567        HAVE_LONG_LONG is not defined.
569    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
570        bring them up to date and include new features. This patch includes:
572        - Fixed PH's badly added libz and libbz2 support.
573        - Fixed a problem with static linking.
574        - Added pcredemo. [But later removed - see 7 below.]
575        - Fixed dftables problem and added an option.
576        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
577            HAVE_LONG_LONG.
578        - Added readline support for pcretest.
579        - Added an listing of the option settings after cmake has run.
581    4.  A user submitted a patch to Makefile that makes it easy to create
582        "pcre.dll" under mingw when using Configure/Make. I added stuff to
583        Makefile.am that cause it to include this special target, without
584        affecting anything else. Note that the same mingw target plus all
585        the other distribution libraries and programs are now supported
586        when configuring with CMake (see 6 below) instead of with
587        Configure/Make.
589    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
590        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
591        exported in the Windows port". It has not yet been confirmed that the patch
592        solves the problem, but it does no harm.
594    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
595        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
596        with CMake, and also correct the comment about stack recursion.
598    7.  Remove the automatic building of pcredemo from the ./configure system and
599        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
600        of a program that users should build themselves after PCRE is installed, so
601        building it automatically is not really right. What is more, it gave
602        trouble in some build environments.
604    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
607    Version 7.5 10-Jan-08
608    ---------------------
610    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
611        values in parens when parsing an RE using the C++ wrapper."
613    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
614        Characters greater than 255 were excluded from the class instead of being
615        included.
617    3.  The same bug as (2) above applied to negated POSIX classes such as
618        [:^space:].
620    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
621        defined or documented. It seems to have been a typo for PCRE_STATIC, so
622        I have changed it.
624    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
625        first named subpattern) and a construct such as (?&a) would reference the
626        first named subpattern whose name started with "a" (in other words, the
627        length check was missing). Both these problems are fixed. "Subpattern name
628        expected" is now given for (?&) (a zero-length name), and this patch also
629        makes it give the same error for \k'' (previously it complained that that
630        was a reference to a non-existent subpattern).
632    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
633        this is right because (?- can be followed by option settings as well as by
634        digits. I have, however, made the messages clearer.
636    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
637        than the number used in the conditional) now cause a compile-time error.
638        This is actually not compatible with Perl, which accepts such patterns, but
639        treats the conditional as always being FALSE (as PCRE used to), but it
640        seems to me that giving a diagnostic is better.
642    8.  Change "alphameric" to the more common word "alphanumeric" in comments
643        and messages.
645    9.  Fix two occurrences of "backslash" in comments that should have been
646        "backspace".
648    10. Remove two redundant lines of code that can never be obeyed (their function
649        was moved elsewhere).
651    11. The program that makes PCRE's Unicode character property table had a bug
652        which caused it to generate incorrect table entries for sequences of
653        characters that have the same character type, but are in different scripts.
654        It amalgamated them into a single range, with the script of the first of
655        them. In other words, some characters were in the wrong script. There were
656        thirteen such cases, affecting characters in the following ranges:
658          U+002b0 - U+002c1
659          U+0060c - U+0060d
660          U+0061e - U+00612
661          U+0064b - U+0065e
662          U+0074d - U+0076d
663          U+01800 - U+01805
664          U+01d00 - U+01d77
665          U+01d9b - U+01dbf
666          U+0200b - U+0200f
667          U+030fc - U+030fe
668          U+03260 - U+0327f
669          U+0fb46 - U+0fbb1
670          U+10450 - U+1049d
672    12. The -o option (show only the matching part of a line) for pcregrep was not
673        compatible with GNU grep in that, if there was more than one match in a
674        line, it showed only the first of them. It now behaves in the same way as
675        GNU grep.
677    13. If the -o and -v options were combined for pcregrep, it printed a blank
678        line for every non-matching line. GNU grep prints nothing, and pcregrep now
679        does the same. The return code can be used to tell if there were any
680        non-matching lines.
682    14. Added --file-offsets and --line-offsets to pcregrep.
684    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
685        infinitely looping recursion. The bug was that positive lookaheads were not
686        being skipped when checking for a possible empty match (negative lookaheads
687        and both kinds of lookbehind were skipped).
689    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
690        inclusion of <windows.h> to before rather than after the definition of
691        INVALID_FILE_ATTRIBUTES (patch from David Byron).
693    17. Specifying a possessive quantifier with a specific limit for a Unicode
694        character property caused pcre_compile() to compile bad code, which led at
695        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
696        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
697        caused the error; without that there was no problem.
699    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
701    19. Added --enable-pcretest-libreadline.
703    20. In pcrecpp.cc, the variable 'count' was incremented twice in
704        RE::GlobalReplace(). As a result, the number of replacements returned was
705        double what it should be. I removed one of the increments, but Craig sent a
706        later patch that removed the other one (the right fix) and added unit tests
707        that check the return values (which was not done before).
709    21. Several CMake things:
711        (1) Arranged that, when cmake is used on Unix, the libraries end up with
712            the names libpcre and libpcreposix, not just pcre and pcreposix.
714        (2) The above change means that pcretest and pcregrep are now correctly
715            linked with the newly-built libraries, not previously installed ones.
719    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
720        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
721        UTF-8 newline character). The key issue is that the pattern starts .*;
722        this means that the match must be either at the beginning, or after a
723        newline. The bug was in the code for advancing after a failed match and
724        checking that the new position followed a newline. It was not taking
725        account of UTF-8 characters correctly.
727    23. PCRE was behaving differently from Perl in the way it recognized POSIX
728        character classes. PCRE was not treating the sequence [:...:] as a
729        character class unless the ... were all letters. Perl, however, seems to
730        allow any characters between [: and :], though of course it rejects as
731        unknown any "names" that contain non-letters, because all the known class
732        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
733        for example, whereas PCRE did not - it did not recognize a POSIX character
734        class. This seemed a bit dangerous, so the code has been changed to be
735        closer to Perl. The behaviour is not identical to Perl, because PCRE will
736        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
737        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
738        Perl does, and where it didn't before.
740    24. Rewrite so as to remove the single use of %n from pcregrep because in some
741        Windows environments %n is disabled by default.
744    Version 7.4 21-Sep-07
745    ---------------------
747    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
748        means that a class such as [\s] counted as "explicit reference to CR or
749        LF". That isn't really right - the whole point of the change was to try to
750        help when there was an actual mention of one of the two characters. So now
751        the change happens only if \r or \n (or a literal CR or LF) character is
752        encountered.
754    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
755        of both had grown to the point where there were only 3 bits left.
756        Fortunately, there was spare space in the data structure, and so I have
757        moved the internal flags into a new 16-bit field to free up more option
758        bits.
760    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
761        but did not set the internal JCHANGED flag - either of these is enough to
762        control the way the "get" function works - but the PCRE_INFO_JCHANGED
763        facility is supposed to tell if (?J) was ever used, so now (?J) at the
764        start sets both bits.
766    4.  Added options (at build time, compile time, exec time) to change \R from
767        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
769    5.  doc/pcresyntax.html was missing from the distribution.
771    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
772        compatibility, even though it is no longer used.
774    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
775        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
776        windows.h file is present (where different names are used). [This was
777        reversed later after testing - see 16 below.]
779    8.  Changed all #include <config.h> to #include "config.h". There were also
780        some further <pcre.h> cases that I changed to "pcre.h".
782    9.  When pcregrep was used with the --colour option, it missed the line ending
783        sequence off the lines that it output.
785    10. It was pointed out to me that arrays of string pointers cause lots of
786        relocations when a shared library is dynamically loaded. A technique of
787        using a single long string with a table of offsets can drastically reduce
788        these. I have refactored PCRE in four places to do this. The result is
789        dramatic:
791          Originally:                          290
792          After changing UCP table:            187
793          After changing error message table:   43
794          After changing table of "verbs"       36
795          After changing table of Posix names   22
797        Thanks to the folks working on Gregex for glib for this insight.
799    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
800        unicode-properties was also set.
802    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
804    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
805        checked only for CRLF.
807    14. Added casts to pcretest.c to avoid compiler warnings.
809    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
811    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
812        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
813        entirely. This removes changes made in 7 above.
815    17. The CMake files have been updated, and there is now more information about
816        building with CMake in the NON-UNIX-USE document.
819    Version 7.3 28-Aug-07
820  ---------------------  ---------------------
822   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 29  Version 7.3 05-Jul-07 Line 844  Version 7.3 05-Jul-07
844   4. Debugging: adjusted the names of opcodes for different kinds of parentheses   4. Debugging: adjusted the names of opcodes for different kinds of parentheses
845      in debug output.      in debug output.
847   5. Arrange to use "%I64d" instead of "%lld" for long printing in the pcrecpp   5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
848      unittest when running under MinGW.      long printing in the pcrecpp unittest when running under MinGW.
850   6. ESC_K was left out of the EBCDIC table.   6. ESC_K was left out of the EBCDIC table.
# Line 53  Version 7.3 05-Jul-07 Line 868  Version 7.3 05-Jul-07
868      pcreposix and pcrecpp parts of the library. These were overlooked when this      pcreposix and pcrecpp parts of the library. These were overlooked when this
869      problem was solved for the main library.      problem was solved for the main library.
871     9. There were some crude static tests to avoid integer overflow when computing
872        the size of patterns that contain repeated groups with explicit upper
873        limits. As the maximum quantifier is 65535, the maximum group length was
874        set at 30,000 so that the product of these two numbers did not overflow a
875        32-bit integer. However, it turns out that people want to use groups that
876        are longer than 30,000 bytes (though not repeat them that many times).
877        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
878        made it possible to implement the integer overflow checks in a much more
879        dynamic way, which I have now done. The artificial limitation on group
880        length has been removed - we now have only the limit on the total length of
881        the compiled pattern, which depends on the LINK_SIZE setting.
883    10. Fixed a bug in the documentation for get/copy named substring when
884        duplicate names are permitted. If none of the named substrings are set, the
885        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
886        empty string.
888    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
889        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
890        because the ] is interpreted as the first data character and the
891        terminating ] is not found. PCRE has been made compatible with Perl in this
892        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
893        cause memory overwriting.
895    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
896        string has been matched (to stop an infinite loop). It was not recognizing
897        a conditional subpattern that could match an empty string if that
898        subpattern was within another subpattern. For example, it looped when
899        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
900        condition was not nested. This bug has been fixed.
902    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
903        past the start of the subject in the presence of bytes with the top bit
904        set, for example "\x8aBCD".
906    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
907        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
909    14. Optimized (?!) to (*FAIL).
911    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
912        This restricts code points to be within the range 0 to 0x10FFFF, excluding
913        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
914        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
915        does: it's just the validity check that is more restrictive.
917    16. Inserted checks for integer overflows during escape sequence (backslash)
918        processing, and also fixed erroneous offset values for syntax errors during
919        backslash processing.
921    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
922        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
924    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
925        caused an overrun.
927    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
928        something other than just ASCII characters) inside a group that had an
929        unlimited repeat caused a loop at compile time (while checking to see
930        whether the group could match an empty string).
932    20. Debugging a pattern containing \p or \P could cause a crash. For example,
933        [\P{Any}] did so. (Error in the code for printing property names.)
935    21. An orphan \E inside a character class could cause a crash.
937    22. A repeated capturing bracket such as (A)? could cause a wild memory
938        reference during compilation.
940    23. There are several functions in pcre_compile() that scan along a compiled
941        expression for various reasons (e.g. to see if it's fixed length for look
942        behind). There were bugs in these functions when a repeated \p or \P was
943        present in the pattern. These operators have additional parameters compared
944        with \d, etc, and these were not being taken into account when moving along
945        the compiled data. Specifically:
947        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
948            length.
950        (b) An item such as \pL+ within a repeated group could cause crashes or
951            loops.
953        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
954            "reference to non-existent subpattern" error.
956        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
958    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
959        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
961    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
963    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
964        character were causing crashes (broken optimization).
966    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
967        \p or \P) caused a compile-time loop.
969    28. More problems have arisen in unanchored patterns when CRLF is a valid line
970        break. For example, the unstudied pattern [\r\n]A does not match the string
971        "\r\nA" because change 7.0/46 below moves the current point on by two
972        characters after failing to match at the start. However, the pattern \nA
973        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
974        the same is true. There doesn't seem any very clean way out of this, but
975        what I have chosen to do makes the common cases work: PCRE now takes note
976        of whether there can be an explicit match for \r or \n anywhere in the
977        pattern, and if so, 7.0/46 no longer applies. As part of this change,
978        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
979        pattern has explicit CR or LF references.
981    29. Added (*CR) etc for changing newline setting at start of pattern.
984  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
985  ---------------------  ---------------------

Removed from v.200  
changed lines
  Added in v.480

  ViewVC Help
Powered by ViewVC 1.1.5