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 428 by ph10, Mon Aug 31 17:10:26 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-07  Version 8.00 ??-???-??
5    ----------------------
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. Chaos could result.
48    9.  The restrictions on what a pattern can contain when partial matching is
49        requested for pcre_exec() have been removed. All patterns can now be
50        partially matched by this function. In addition, if there are at least two
51        slots in the offset vector, the offsets of the first-encountered partial
52        match are set in them when PCRE_ERROR_PARTIAL is returned.
54    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
55        synonymous with PCRE_PARTIAL, for backwards compatibility, and
56        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
57        and may be more useful for multi-segment matching, especially with
58        pcre_exec().
60    11. Partial matching with pcre_exec() is now more intuitive. A partial match
61        used to be given if ever the end of the subject was reached; now it is
62        given only if matching could not proceed because another character was
63        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
64        string "Z", which now yields "no match" instead of "partial match". In the
65        case of pcre_dfa_exec(), "no match" is given if every matching path for the
66        final character ended with (*FAIL).
68    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
69        if the pattern had a "must contain" character that was already found in the
70        earlier partial match, unless partial matching was again requested. For
71        example, with the pattern /dog.(body)?/, the "must contain" character is
72        "g". If the first part-match was for the string "dog", restarting with
73        "sbody" failed.
76    Version 7.9 11-Apr-09
77    ---------------------
79    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
80        (pcretest), all targets were linked against these libraries. This included
81        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
82        libraries. This caused unwanted dependencies to be created. This problem
83        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
84        pcretest is linked with readline.
86    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
87        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
88        moved outside it again, because FALSE and TRUE are already defined in AIX,
89        but BOOL is not.
91    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
92        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
94    4.  The pcregrep documentation said spaces were inserted as well as colons (or
95        hyphens) following file names and line numbers when outputting matching
96        lines. This is not true; no spaces are inserted. I have also clarified the
97        wording for the --colour (or --color) option.
99    5.  In pcregrep, when --colour was used with -o, the list of matching strings
100        was not coloured; this is different to GNU grep, so I have changed it to be
101        the same.
103    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
104        each matching line was coloured. Now it goes on to look for further matches
105        of any of the test patterns, which is the same behaviour as GNU grep.
107    7.  A pattern that could match an empty string could cause pcregrep to loop; it
108        doesn't make sense to accept an empty string match in pcregrep, so I have
109        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
110        seems to be how GNU grep behaves.
112    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
113        start or after a newline", because the conditional assertion was not being
114        correctly handled. The rule now is that both the assertion and what follows
115        in the first alternative must satisfy the test.
117    9.  If auto-callout was enabled in a pattern with a conditional group whose
118        condition was an assertion, PCRE could crash during matching, both with
119        pcre_exec() and pcre_dfa_exec().
121    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
122        used for matching.
124    11. Unicode property support in character classes was not working for
125        characters (bytes) greater than 127 when not in UTF-8 mode.
127    12. Added the -M command line option to pcretest.
129    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
131    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
133    16. Added comments and documentation about mis-use of no_arg in the C++
134        wrapper.
136    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
137        from Martin Jerabek that uses macro names for all relevant character and
138        string constants.
140    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
141        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
142        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
143        these, but not everybody uses configure.
145    19. A conditional group that had only one branch was not being correctly
146        recognized as an item that could match an empty string. This meant that an
147        enclosing group might also not be so recognized, causing infinite looping
148        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
149        with the subject "ab", where knowledge that the repeated group can match
150        nothing is needed in order to break the loop.
152    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
153        exec(), but without supplying a callout function, matching went wrong.
155    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
156        leak if the size of the offset vector was greater than 30. When the vector
157        is smaller, the saved offsets during recursion go onto a local stack
158        vector, but for larger vectors malloc() is used. It was failing to free
159        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
160        error, in fact).
162    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
163        heapframe that is used only when UTF-8 support is enabled. This caused no
164        problem, but was untidy.
166    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
167        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
168        included within another project.
170    24. Steven Van Ingelgem's patches to add more options to the CMake support,
171        slightly modified by me:
173          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
174              not building pcregrep.
176          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
177              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
179    25. Forward references, both numeric and by name, in patterns that made use of
180        duplicate group numbers, could behave incorrectly or give incorrect errors,
181        because when scanning forward to find the reference group, PCRE was not
182        taking into account the duplicate group numbers. A pattern such as
183        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
185    26. Changed a few more instances of "const unsigned char *" to USPTR, making
186        the feature of a custom pointer more persuasive (as requested by a user).
188    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
189        pcretest.c, inside #ifndefs, because it seems they are sometimes already
190        pre-defined.
192    28. Added support for (*UTF8) at the start of a pattern.
194    29. Arrange for flags added by the "release type" setting in CMake to be shown
195        in the configuration summary.
198    Version 7.8 05-Sep-08
199    ---------------------
201    1.  Replaced UCP searching code with optimized version as implemented for Ad
202        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
203        stage table and inline lookup instead of a function, giving speed ups of 2
204        to 5 times on some simple patterns that I tested. Permission was given to
205        distribute the MultiStage2.py script that generates the tables (it's not in
206        the tarball, but is in the Subversion repository).
208    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
209        scripts.
211    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
212        a group with a zero qualifier. The result of the study could be incorrect,
213        or the function might crash, depending on the pattern.
215    4.  Caseless matching was not working for non-ASCII characters in back
216        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
217        It now works when Unicode Property Support is available.
219    5.  In pcretest, an escape such as \x{de} in the data was always generating
220        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
221        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
222        truncation.
224    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
226    7.  Added two (int) casts to pcregrep when printing the difference of two
227        pointers, in case they are 64-bit values.
229    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
230        test 2 if it fails.
232    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
233        and a #define of that name to empty if it is not externally set. This is to
234        allow users of MSVC to set it if necessary.
236    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
237        the convenience functions in the pcre_get.c source file.
239    11. An option change at the start of a pattern that had top-level alternatives
240        could cause overwriting and/or a crash. This command provoked a crash in
241        some environments:
243          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
245        This potential security problem was recorded as CVE-2008-2371.
247    12. For a pattern where the match had to start at the beginning or immediately
248        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
249        pcre_dfa_exec() could read past the end of the passed subject if there was
250        no match. To help with detecting such bugs (e.g. with valgrind), I modified
251        pcretest so that it places the subject at the end of its malloc-ed buffer.
253    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
254        exec() might read past the end of the data buffer in UTF-8 mode.
256    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
257        the data contained the byte 0x85 as part of a UTF-8 character within its
258        first line. This applied both to normal and DFA matching.
260    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
261        /^[^d]*?$/8 failed to match "abc".
263    16. Added a missing copyright notice to pcrecpp_internal.h.
265    17. Make it more clear in the documentation that values returned from
266        pcre_exec() in ovector are byte offsets, not character counts.
268    18. Tidied a few places to stop certain compilers from issuing warnings.
270    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
271        supplied by Stefan Weber. I made a further small update for 7.8 because
272        there is a change of source arrangements: the pcre_searchfuncs.c module is
273        replaced by pcre_ucd.c.
276    Version 7.7 07-May-08
277    ---------------------
279    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
280        a string to a long long, pretend we don't even have a long long." This is
281        done by checking for the strtoq, strtoll, and _strtoi64 functions.
283    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
284        pre-7.6 versions, which defined a global no_arg variable instead of putting
285        it in the RE class. (See also #8 below.)
287    3.  Remove a line of dead code, identified by coverity and reported by Nuno
288        Lopes.
290    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
292        (1) The include/exclude patterns were being applied to the whole pathnames
293            of files, instead of just to the final components.
295        (2) If there was more than one level of directory, the subdirectories were
296            skipped unless they satisfied the include/exclude conditions. This is
297            inconsistent with GNU grep (and could even be seen as contrary to the
298            pcregrep specification - which I improved to make it absolutely clear).
299            The action now is always to scan all levels of directory, and just
300            apply the include/exclude patterns to regular files.
302    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
303        --exclude_dir in the tests to avoid scanning .svn directories.
305    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
306        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
307        doesn't support NULs in patterns.
309    7.  Added some missing "const"s to declarations of static tables in
310        pcre_compile.c and pcre_dfa_exec.c.
312    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
313        caused by fix #2  above. (Subsequently also a second patch to fix the
314        first patch. And a third patch - this was a messy problem.)
316    9.  Applied Craig's patch to remove the use of push_back().
318    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
319        matching function regexec().
321    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
322        which, however, unlike Perl's \g{...}, are subroutine calls, not back
323        references. PCRE supports relative numbers with this syntax (I don't think
324        Oniguruma does).
326    12. Previously, a group with a zero repeat such as (...){0} was completely
327        omitted from the compiled regex. However, this means that if the group
328        was called as a subroutine from elsewhere in the pattern, things went wrong
329        (an internal error was given). Such groups are now left in the compiled
330        pattern, with a new opcode that causes them to be skipped at execution
331        time.
333    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
334        to the way PCRE behaves:
336        (a) A lone ] character is dis-allowed (Perl treats it as data).
338        (b) A back reference to an unmatched subpattern matches an empty string
339            (Perl fails the current match path).
341        (c) A data ] in a character class must be notated as \] because if the
342            first data character in a class is ], it defines an empty class. (In
343            Perl it is not possible to have an empty class.) The empty class []
344            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
345            The negative empty class [^] matches any one character, independently
346            of the DOTALL setting.
348    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
349        non-existent subpattern following a character class starting with ']' and
350        containing () gave an internal compiling error instead of "reference to
351        non-existent subpattern". Fortunately, when the pattern did exist, the
352        compiled code was correct. (When scanning forwards to check for the
353        existencd of the subpattern, it was treating the data ']' as terminating
354        the class, so got the count wrong. When actually compiling, the reference
355        was subsequently set up correctly.)
357    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
358        it was being rejected as not supported by pcre_dfa_exec(), even though
359        other assertions are supported. I have made pcre_dfa_exec() support
360        (*FAIL).
362    16. The implementation of 13c above involved the invention of a new opcode,
363        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
364        cannot be changed at match time, I realized I could make a small
365        improvement to matching performance by compiling OP_ALLANY instead of
366        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
367        on the OP_ANY path.
369    17. Compiling pcretest on Windows with readline support failed without the
370        following two fixes: (1) Make the unistd.h include conditional on
371        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
373    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
374        ncurses library to be included for pcretest when ReadLine support is
375        requested, but also to allow for it to be overridden. This patch came from
376        Daniel Bergström.
378    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
379        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
380        any errors with the current Unicode tables. Thanks to Peter Kankowski for
381        spotting this.
384    Version 7.6 28-Jan-08
385    ---------------------
387    1.  A character class containing a very large number of characters with
388        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
389        overflow.
391    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
392        HAVE_LONG_LONG is not defined.
394    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
395        bring them up to date and include new features. This patch includes:
397        - Fixed PH's badly added libz and libbz2 support.
398        - Fixed a problem with static linking.
399        - Added pcredemo. [But later removed - see 7 below.]
400        - Fixed dftables problem and added an option.
401        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
402            HAVE_LONG_LONG.
403        - Added readline support for pcretest.
404        - Added an listing of the option settings after cmake has run.
406    4.  A user submitted a patch to Makefile that makes it easy to create
407        "pcre.dll" under mingw when using Configure/Make. I added stuff to
408        Makefile.am that cause it to include this special target, without
409        affecting anything else. Note that the same mingw target plus all
410        the other distribution libraries and programs are now supported
411        when configuring with CMake (see 6 below) instead of with
412        Configure/Make.
414    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
415        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
416        exported in the Windows port". It has not yet been confirmed that the patch
417        solves the problem, but it does no harm.
419    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
420        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
421        with CMake, and also correct the comment about stack recursion.
423    7.  Remove the automatic building of pcredemo from the ./configure system and
424        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
425        of a program that users should build themselves after PCRE is installed, so
426        building it automatically is not really right. What is more, it gave
427        trouble in some build environments.
429    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
432    Version 7.5 10-Jan-08
433    ---------------------
435    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
436        values in parens when parsing an RE using the C++ wrapper."
438    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
439        Characters greater than 255 were excluded from the class instead of being
440        included.
442    3.  The same bug as (2) above applied to negated POSIX classes such as
443        [:^space:].
445    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
446        defined or documented. It seems to have been a typo for PCRE_STATIC, so
447        I have changed it.
449    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
450        first named subpattern) and a construct such as (?&a) would reference the
451        first named subpattern whose name started with "a" (in other words, the
452        length check was missing). Both these problems are fixed. "Subpattern name
453        expected" is now given for (?&) (a zero-length name), and this patch also
454        makes it give the same error for \k'' (previously it complained that that
455        was a reference to a non-existent subpattern).
457    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
458        this is right because (?- can be followed by option settings as well as by
459        digits. I have, however, made the messages clearer.
461    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
462        than the number used in the conditional) now cause a compile-time error.
463        This is actually not compatible with Perl, which accepts such patterns, but
464        treats the conditional as always being FALSE (as PCRE used to), but it
465        seems to me that giving a diagnostic is better.
467    8.  Change "alphameric" to the more common word "alphanumeric" in comments
468        and messages.
470    9.  Fix two occurrences of "backslash" in comments that should have been
471        "backspace".
473    10. Remove two redundant lines of code that can never be obeyed (their function
474        was moved elsewhere).
476    11. The program that makes PCRE's Unicode character property table had a bug
477        which caused it to generate incorrect table entries for sequences of
478        characters that have the same character type, but are in different scripts.
479        It amalgamated them into a single range, with the script of the first of
480        them. In other words, some characters were in the wrong script. There were
481        thirteen such cases, affecting characters in the following ranges:
483          U+002b0 - U+002c1
484          U+0060c - U+0060d
485          U+0061e - U+00612
486          U+0064b - U+0065e
487          U+0074d - U+0076d
488          U+01800 - U+01805
489          U+01d00 - U+01d77
490          U+01d9b - U+01dbf
491          U+0200b - U+0200f
492          U+030fc - U+030fe
493          U+03260 - U+0327f
494          U+0fb46 - U+0fbb1
495          U+10450 - U+1049d
497    12. The -o option (show only the matching part of a line) for pcregrep was not
498        compatible with GNU grep in that, if there was more than one match in a
499        line, it showed only the first of them. It now behaves in the same way as
500        GNU grep.
502    13. If the -o and -v options were combined for pcregrep, it printed a blank
503        line for every non-matching line. GNU grep prints nothing, and pcregrep now
504        does the same. The return code can be used to tell if there were any
505        non-matching lines.
507    14. Added --file-offsets and --line-offsets to pcregrep.
509    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
510        infinitely looping recursion. The bug was that positive lookaheads were not
511        being skipped when checking for a possible empty match (negative lookaheads
512        and both kinds of lookbehind were skipped).
514    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
515        inclusion of <windows.h> to before rather than after the definition of
516        INVALID_FILE_ATTRIBUTES (patch from David Byron).
518    17. Specifying a possessive quantifier with a specific limit for a Unicode
519        character property caused pcre_compile() to compile bad code, which led at
520        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
521        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
522        caused the error; without that there was no problem.
524    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
526    19. Added --enable-pcretest-libreadline.
528    20. In pcrecpp.cc, the variable 'count' was incremented twice in
529        RE::GlobalReplace(). As a result, the number of replacements returned was
530        double what it should be. I removed one of the increments, but Craig sent a
531        later patch that removed the other one (the right fix) and added unit tests
532        that check the return values (which was not done before).
534    21. Several CMake things:
536        (1) Arranged that, when cmake is used on Unix, the libraries end up with
537            the names libpcre and libpcreposix, not just pcre and pcreposix.
539        (2) The above change means that pcretest and pcregrep are now correctly
540            linked with the newly-built libraries, not previously installed ones.
544    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
545        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
546        UTF-8 newline character). The key issue is that the pattern starts .*;
547        this means that the match must be either at the beginning, or after a
548        newline. The bug was in the code for advancing after a failed match and
549        checking that the new position followed a newline. It was not taking
550        account of UTF-8 characters correctly.
552    23. PCRE was behaving differently from Perl in the way it recognized POSIX
553        character classes. PCRE was not treating the sequence [:...:] as a
554        character class unless the ... were all letters. Perl, however, seems to
555        allow any characters between [: and :], though of course it rejects as
556        unknown any "names" that contain non-letters, because all the known class
557        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
558        for example, whereas PCRE did not - it did not recognize a POSIX character
559        class. This seemed a bit dangerous, so the code has been changed to be
560        closer to Perl. The behaviour is not identical to Perl, because PCRE will
561        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
562        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
563        Perl does, and where it didn't before.
565    24. Rewrite so as to remove the single use of %n from pcregrep because in some
566        Windows environments %n is disabled by default.
569    Version 7.4 21-Sep-07
570    ---------------------
572    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
573        means that a class such as [\s] counted as "explicit reference to CR or
574        LF". That isn't really right - the whole point of the change was to try to
575        help when there was an actual mention of one of the two characters. So now
576        the change happens only if \r or \n (or a literal CR or LF) character is
577        encountered.
579    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
580        of both had grown to the point where there were only 3 bits left.
581        Fortunately, there was spare space in the data structure, and so I have
582        moved the internal flags into a new 16-bit field to free up more option
583        bits.
585    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
586        but did not set the internal JCHANGED flag - either of these is enough to
587        control the way the "get" function works - but the PCRE_INFO_JCHANGED
588        facility is supposed to tell if (?J) was ever used, so now (?J) at the
589        start sets both bits.
591    4.  Added options (at build time, compile time, exec time) to change \R from
592        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
594    5.  doc/pcresyntax.html was missing from the distribution.
596    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
597        compatibility, even though it is no longer used.
599    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
600        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
601        windows.h file is present (where different names are used). [This was
602        reversed later after testing - see 16 below.]
604    8.  Changed all #include <config.h> to #include "config.h". There were also
605        some further <pcre.h> cases that I changed to "pcre.h".
607    9.  When pcregrep was used with the --colour option, it missed the line ending
608        sequence off the lines that it output.
610    10. It was pointed out to me that arrays of string pointers cause lots of
611        relocations when a shared library is dynamically loaded. A technique of
612        using a single long string with a table of offsets can drastically reduce
613        these. I have refactored PCRE in four places to do this. The result is
614        dramatic:
616          Originally:                          290
617          After changing UCP table:            187
618          After changing error message table:   43
619          After changing table of "verbs"       36
620          After changing table of Posix names   22
622        Thanks to the folks working on Gregex for glib for this insight.
624    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
625        unicode-properties was also set.
627    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
629    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
630        checked only for CRLF.
632    14. Added casts to pcretest.c to avoid compiler warnings.
634    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
636    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
637        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
638        entirely. This removes changes made in 7 above.
640    17. The CMake files have been updated, and there is now more information about
641        building with CMake in the NON-UNIX-USE document.
644    Version 7.3 28-Aug-07
645  ---------------------  ---------------------
647   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 669  Version 7.3 05-Jul-07
669   4. Debugging: adjusted the names of opcodes for different kinds of parentheses   4. Debugging: adjusted the names of opcodes for different kinds of parentheses
670      in debug output.      in debug output.
672   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
673      unittest when running under MinGW.      long printing in the pcrecpp unittest when running under MinGW.
675   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 693  Version 7.3 05-Jul-07
693      pcreposix and pcrecpp parts of the library. These were overlooked when this      pcreposix and pcrecpp parts of the library. These were overlooked when this
694      problem was solved for the main library.      problem was solved for the main library.
696     9. There were some crude static tests to avoid integer overflow when computing
697        the size of patterns that contain repeated groups with explicit upper
698        limits. As the maximum quantifier is 65535, the maximum group length was
699        set at 30,000 so that the product of these two numbers did not overflow a
700        32-bit integer. However, it turns out that people want to use groups that
701        are longer than 30,000 bytes (though not repeat them that many times).
702        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
703        made it possible to implement the integer overflow checks in a much more
704        dynamic way, which I have now done. The artificial limitation on group
705        length has been removed - we now have only the limit on the total length of
706        the compiled pattern, which depends on the LINK_SIZE setting.
708    10. Fixed a bug in the documentation for get/copy named substring when
709        duplicate names are permitted. If none of the named substrings are set, the
710        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
711        empty string.
713    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
714        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
715        because the ] is interpreted as the first data character and the
716        terminating ] is not found. PCRE has been made compatible with Perl in this
717        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
718        cause memory overwriting.
720    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
721        string has been matched (to stop an infinite loop). It was not recognizing
722        a conditional subpattern that could match an empty string if that
723        subpattern was within another subpattern. For example, it looped when
724        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
725        condition was not nested. This bug has been fixed.
727    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
728        past the start of the subject in the presence of bytes with the top bit
729        set, for example "\x8aBCD".
731    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
732        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
734    14. Optimized (?!) to (*FAIL).
736    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
737        This restricts code points to be within the range 0 to 0x10FFFF, excluding
738        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
739        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
740        does: it's just the validity check that is more restrictive.
742    16. Inserted checks for integer overflows during escape sequence (backslash)
743        processing, and also fixed erroneous offset values for syntax errors during
744        backslash processing.
746    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
747        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
749    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
750        caused an overrun.
752    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
753        something other than just ASCII characters) inside a group that had an
754        unlimited repeat caused a loop at compile time (while checking to see
755        whether the group could match an empty string).
757    20. Debugging a pattern containing \p or \P could cause a crash. For example,
758        [\P{Any}] did so. (Error in the code for printing property names.)
760    21. An orphan \E inside a character class could cause a crash.
762    22. A repeated capturing bracket such as (A)? could cause a wild memory
763        reference during compilation.
765    23. There are several functions in pcre_compile() that scan along a compiled
766        expression for various reasons (e.g. to see if it's fixed length for look
767        behind). There were bugs in these functions when a repeated \p or \P was
768        present in the pattern. These operators have additional parameters compared
769        with \d, etc, and these were not being taken into account when moving along
770        the compiled data. Specifically:
772        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
773            length.
775        (b) An item such as \pL+ within a repeated group could cause crashes or
776            loops.
778        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
779            "reference to non-existent subpattern" error.
781        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
783    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
784        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
786    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
788    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
789        character were causing crashes (broken optimization).
791    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
792        \p or \P) caused a compile-time loop.
794    28. More problems have arisen in unanchored patterns when CRLF is a valid line
795        break. For example, the unstudied pattern [\r\n]A does not match the string
796        "\r\nA" because change 7.0/46 below moves the current point on by two
797        characters after failing to match at the start. However, the pattern \nA
798        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
799        the same is true. There doesn't seem any very clean way out of this, but
800        what I have chosen to do makes the common cases work: PCRE now takes note
801        of whether there can be an explicit match for \r or \n anywhere in the
802        pattern, and if so, 7.0/46 no longer applies. As part of this change,
803        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
804        pattern has explicit CR or LF references.
806    29. Added (*CR) etc for changing newline setting at start of pattern.
809  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
810  ---------------------  ---------------------

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

  ViewVC Help
Powered by ViewVC 1.1.5