ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 179 by ph10, Wed Jun 13 08:53:45 2007 UTC revision 388 by ph10, Wed Mar 11 17:03:17 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 05-June-07  Version 7.9 xx-xxx-09
5    ---------------------
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
45    9.  If auto-callout was enabled in a pattern with a conditional group, PCRE
46        could crash during matching.
48    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
49        used for matching.
51    11. Unicode property support in character classes was not working for
52        characters (bytes) greater than 127 when not in UTF-8 mode.
54    12. Added the -M command line option to pcretest.
56    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    Version 7.8 05-Sep-08
60    ---------------------
62    1.  Replaced UCP searching code with optimized version as implemented for Ad
63        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
64        stage table and inline lookup instead of a function, giving speed ups of 2
65        to 5 times on some simple patterns that I tested. Permission was given to
66        distribute the MultiStage2.py script that generates the tables (it's not in
67        the tarball, but is in the Subversion repository).
69    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
70        scripts.
72    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
73        a group with a zero qualifier. The result of the study could be incorrect,
74        or the function might crash, depending on the pattern.
76    4.  Caseless matching was not working for non-ASCII characters in back
77        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
78        It now works when Unicode Property Support is available.
80    5.  In pcretest, an escape such as \x{de} in the data was always generating
81        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
82        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
83        truncation.
85    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
87    7.  Added two (int) casts to pcregrep when printing the difference of two
88        pointers, in case they are 64-bit values.
90    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
91        test 2 if it fails.
93    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
94        and a #define of that name to empty if it is not externally set. This is to
95        allow users of MSVC to set it if necessary.
97    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
98        the convenience functions in the pcre_get.c source file.
100    11. An option change at the start of a pattern that had top-level alternatives
101        could cause overwriting and/or a crash. This command provoked a crash in
102        some environments:
104          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
106        This potential security problem was recorded as CVE-2008-2371.
108    12. For a pattern where the match had to start at the beginning or immediately
109        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
110        pcre_dfa_exec() could read past the end of the passed subject if there was
111        no match. To help with detecting such bugs (e.g. with valgrind), I modified
112        pcretest so that it places the subject at the end of its malloc-ed buffer.
114    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
115        exec() might read past the end of the data buffer in UTF-8 mode.
117    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
118        the data contained the byte 0x85 as part of a UTF-8 character within its
119        first line. This applied both to normal and DFA matching.
121    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
122        /^[^d]*?$/8 failed to match "abc".
124    16. Added a missing copyright notice to pcrecpp_internal.h.
126    17. Make it more clear in the documentation that values returned from
127        pcre_exec() in ovector are byte offsets, not character counts.
129    18. Tidied a few places to stop certain compilers from issuing warnings.
131    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
132        supplied by Stefan Weber. I made a further small update for 7.8 because
133        there is a change of source arrangements: the pcre_searchfuncs.c module is
134        replaced by pcre_ucd.c.
137    Version 7.7 07-May-08
138    ---------------------
140    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
141        a string to a long long, pretend we don't even have a long long." This is
142        done by checking for the strtoq, strtoll, and _strtoi64 functions.
144    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
145        pre-7.6 versions, which defined a global no_arg variable instead of putting
146        it in the RE class. (See also #8 below.)
148    3.  Remove a line of dead code, identified by coverity and reported by Nuno
149        Lopes.
151    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
153        (1) The include/exclude patterns were being applied to the whole pathnames
154            of files, instead of just to the final components.
156        (2) If there was more than one level of directory, the subdirectories were
157            skipped unless they satisfied the include/exclude conditions. This is
158            inconsistent with GNU grep (and could even be seen as contrary to the
159            pcregrep specification - which I improved to make it absolutely clear).
160            The action now is always to scan all levels of directory, and just
161            apply the include/exclude patterns to regular files.
163    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
164        --exclude_dir in the tests to avoid scanning .svn directories.
166    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
167        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
168        doesn't support NULs in patterns.
170    7.  Added some missing "const"s to declarations of static tables in
171        pcre_compile.c and pcre_dfa_exec.c.
173    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
174        caused by fix #2  above. (Subsequently also a second patch to fix the
175        first patch. And a third patch - this was a messy problem.)
177    9.  Applied Craig's patch to remove the use of push_back().
179    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
180        matching function regexec().
182    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
183        which, however, unlike Perl's \g{...}, are subroutine calls, not back
184        references. PCRE supports relative numbers with this syntax (I don't think
185        Oniguruma does).
187    12. Previously, a group with a zero repeat such as (...){0} was completely
188        omitted from the compiled regex. However, this means that if the group
189        was called as a subroutine from elsewhere in the pattern, things went wrong
190        (an internal error was given). Such groups are now left in the compiled
191        pattern, with a new opcode that causes them to be skipped at execution
192        time.
194    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
195        to the way PCRE behaves:
197        (a) A lone ] character is dis-allowed (Perl treats it as data).
199        (b) A back reference to an unmatched subpattern matches an empty string
200            (Perl fails the current match path).
202        (c) A data ] in a character class must be notated as \] because if the
203            first data character in a class is ], it defines an empty class. (In
204            Perl it is not possible to have an empty class.) The empty class []
205            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
206            The negative empty class [^] matches any one character, independently
207            of the DOTALL setting.
209    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
210        non-existent subpattern following a character class starting with ']' and
211        containing () gave an internal compiling error instead of "reference to
212        non-existent subpattern". Fortunately, when the pattern did exist, the
213        compiled code was correct. (When scanning forwards to check for the
214        existencd of the subpattern, it was treating the data ']' as terminating
215        the class, so got the count wrong. When actually compiling, the reference
216        was subsequently set up correctly.)
218    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
219        it was being rejected as not supported by pcre_dfa_exec(), even though
220        other assertions are supported. I have made pcre_dfa_exec() support
221        (*FAIL).
223    16. The implementation of 13c above involved the invention of a new opcode,
224        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
225        cannot be changed at match time, I realized I could make a small
226        improvement to matching performance by compiling OP_ALLANY instead of
227        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
228        on the OP_ANY path.
230    17. Compiling pcretest on Windows with readline support failed without the
231        following two fixes: (1) Make the unistd.h include conditional on
232        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
234    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
235        ncurses library to be included for pcretest when ReadLine support is
236        requested, but also to allow for it to be overridden. This patch came from
237        Daniel Bergström.
239    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
240        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
241        any errors with the current Unicode tables. Thanks to Peter Kankowski for
242        spotting this.
245    Version 7.6 28-Jan-08
246    ---------------------
248    1.  A character class containing a very large number of characters with
249        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
250        overflow.
252    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
253        HAVE_LONG_LONG is not defined.
255    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
256        bring them up to date and include new features. This patch includes:
258        - Fixed PH's badly added libz and libbz2 support.
259        - Fixed a problem with static linking.
260        - Added pcredemo. [But later removed - see 7 below.]
261        - Fixed dftables problem and added an option.
262        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
263            HAVE_LONG_LONG.
264        - Added readline support for pcretest.
265        - Added an listing of the option settings after cmake has run.
267    4.  A user submitted a patch to Makefile that makes it easy to create
268        "pcre.dll" under mingw when using Configure/Make. I added stuff to
269        Makefile.am that cause it to include this special target, without
270        affecting anything else. Note that the same mingw target plus all
271        the other distribution libraries and programs are now supported
272        when configuring with CMake (see 6 below) instead of with
273        Configure/Make.
275    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
276        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
277        exported in the Windows port". It has not yet been confirmed that the patch
278        solves the problem, but it does no harm.
280    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
281        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
282        with CMake, and also correct the comment about stack recursion.
284    7.  Remove the automatic building of pcredemo from the ./configure system and
285        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
286        of a program that users should build themselves after PCRE is installed, so
287        building it automatically is not really right. What is more, it gave
288        trouble in some build environments.
290    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
293    Version 7.5 10-Jan-08
294    ---------------------
296    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
297        values in parens when parsing an RE using the C++ wrapper."
299    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
300        Characters greater than 255 were excluded from the class instead of being
301        included.
303    3.  The same bug as (2) above applied to negated POSIX classes such as
304        [:^space:].
306    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
307        defined or documented. It seems to have been a typo for PCRE_STATIC, so
308        I have changed it.
310    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
311        first named subpattern) and a construct such as (?&a) would reference the
312        first named subpattern whose name started with "a" (in other words, the
313        length check was missing). Both these problems are fixed. "Subpattern name
314        expected" is now given for (?&) (a zero-length name), and this patch also
315        makes it give the same error for \k'' (previously it complained that that
316        was a reference to a non-existent subpattern).
318    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
319        this is right because (?- can be followed by option settings as well as by
320        digits. I have, however, made the messages clearer.
322    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
323        than the number used in the conditional) now cause a compile-time error.
324        This is actually not compatible with Perl, which accepts such patterns, but
325        treats the conditional as always being FALSE (as PCRE used to), but it
326        seems to me that giving a diagnostic is better.
328    8.  Change "alphameric" to the more common word "alphanumeric" in comments
329        and messages.
331    9.  Fix two occurrences of "backslash" in comments that should have been
332        "backspace".
334    10. Remove two redundant lines of code that can never be obeyed (their function
335        was moved elsewhere).
337    11. The program that makes PCRE's Unicode character property table had a bug
338        which caused it to generate incorrect table entries for sequences of
339        characters that have the same character type, but are in different scripts.
340        It amalgamated them into a single range, with the script of the first of
341        them. In other words, some characters were in the wrong script. There were
342        thirteen such cases, affecting characters in the following ranges:
344          U+002b0 - U+002c1
345          U+0060c - U+0060d
346          U+0061e - U+00612
347          U+0064b - U+0065e
348          U+0074d - U+0076d
349          U+01800 - U+01805
350          U+01d00 - U+01d77
351          U+01d9b - U+01dbf
352          U+0200b - U+0200f
353          U+030fc - U+030fe
354          U+03260 - U+0327f
355          U+0fb46 - U+0fbb1
356          U+10450 - U+1049d
358    12. The -o option (show only the matching part of a line) for pcregrep was not
359        compatible with GNU grep in that, if there was more than one match in a
360        line, it showed only the first of them. It now behaves in the same way as
361        GNU grep.
363    13. If the -o and -v options were combined for pcregrep, it printed a blank
364        line for every non-matching line. GNU grep prints nothing, and pcregrep now
365        does the same. The return code can be used to tell if there were any
366        non-matching lines.
368    14. Added --file-offsets and --line-offsets to pcregrep.
370    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
371        infinitely looping recursion. The bug was that positive lookaheads were not
372        being skipped when checking for a possible empty match (negative lookaheads
373        and both kinds of lookbehind were skipped).
375    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
376        inclusion of <windows.h> to before rather than after the definition of
377        INVALID_FILE_ATTRIBUTES (patch from David Byron).
379    17. Specifying a possessive quantifier with a specific limit for a Unicode
380        character property caused pcre_compile() to compile bad code, which led at
381        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
382        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
383        caused the error; without that there was no problem.
385    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
387    19. Added --enable-pcretest-libreadline.
389    20. In pcrecpp.cc, the variable 'count' was incremented twice in
390        RE::GlobalReplace(). As a result, the number of replacements returned was
391        double what it should be. I removed one of the increments, but Craig sent a
392        later patch that removed the other one (the right fix) and added unit tests
393        that check the return values (which was not done before).
395    21. Several CMake things:
397        (1) Arranged that, when cmake is used on Unix, the libraries end up with
398            the names libpcre and libpcreposix, not just pcre and pcreposix.
400        (2) The above change means that pcretest and pcregrep are now correctly
401            linked with the newly-built libraries, not previously installed ones.
405    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
406        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
407        UTF-8 newline character). The key issue is that the pattern starts .*;
408        this means that the match must be either at the beginning, or after a
409        newline. The bug was in the code for advancing after a failed match and
410        checking that the new position followed a newline. It was not taking
411        account of UTF-8 characters correctly.
413    23. PCRE was behaving differently from Perl in the way it recognized POSIX
414        character classes. PCRE was not treating the sequence [:...:] as a
415        character class unless the ... were all letters. Perl, however, seems to
416        allow any characters between [: and :], though of course it rejects as
417        unknown any "names" that contain non-letters, because all the known class
418        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
419        for example, whereas PCRE did not - it did not recognize a POSIX character
420        class. This seemed a bit dangerous, so the code has been changed to be
421        closer to Perl. The behaviour is not identical to Perl, because PCRE will
422        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
423        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
424        Perl does, and where it didn't before.
426    24. Rewrite so as to remove the single use of %n from pcregrep because in some
427        Windows environments %n is disabled by default.
430    Version 7.4 21-Sep-07
431    ---------------------
433    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
434        means that a class such as [\s] counted as "explicit reference to CR or
435        LF". That isn't really right - the whole point of the change was to try to
436        help when there was an actual mention of one of the two characters. So now
437        the change happens only if \r or \n (or a literal CR or LF) character is
438        encountered.
440    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
441        of both had grown to the point where there were only 3 bits left.
442        Fortunately, there was spare space in the data structure, and so I have
443        moved the internal flags into a new 16-bit field to free up more option
444        bits.
446    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
447        but did not set the internal JCHANGED flag - either of these is enough to
448        control the way the "get" function works - but the PCRE_INFO_JCHANGED
449        facility is supposed to tell if (?J) was ever used, so now (?J) at the
450        start sets both bits.
452    4.  Added options (at build time, compile time, exec time) to change \R from
453        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
455    5.  doc/pcresyntax.html was missing from the distribution.
457    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
458        compatibility, even though it is no longer used.
460    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
461        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
462        windows.h file is present (where different names are used). [This was
463        reversed later after testing - see 16 below.]
465    8.  Changed all #include <config.h> to #include "config.h". There were also
466        some further <pcre.h> cases that I changed to "pcre.h".
468    9.  When pcregrep was used with the --colour option, it missed the line ending
469        sequence off the lines that it output.
471    10. It was pointed out to me that arrays of string pointers cause lots of
472        relocations when a shared library is dynamically loaded. A technique of
473        using a single long string with a table of offsets can drastically reduce
474        these. I have refactored PCRE in four places to do this. The result is
475        dramatic:
477          Originally:                          290
478          After changing UCP table:            187
479          After changing error message table:   43
480          After changing table of "verbs"       36
481          After changing table of Posix names   22
483        Thanks to the folks working on Gregex for glib for this insight.
485    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
486        unicode-properties was also set.
488    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
490    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
491        checked only for CRLF.
493    14. Added casts to pcretest.c to avoid compiler warnings.
495    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
497    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
498        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
499        entirely. This removes changes made in 7 above.
501    17. The CMake files have been updated, and there is now more information about
502        building with CMake in the NON-UNIX-USE document.
505    Version 7.3 28-Aug-07
506    ---------------------
508     1. In the rejigging of the build system that eventually resulted in 7.1, the
509        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
510        brackets there is not right, since it causes compilers to look for an
511        installed pcre.h, not the version that is in the source that is being
512        compiled (which of course may be different). I have changed it back to:
514          #include "pcre.h"
516        I have a vague recollection that the change was concerned with compiling in
517        different directories, but in the new build system, that is taken care of
518        by the VPATH setting the Makefile.
520     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
521        when the subject happened to end in the byte 0x85 (e.g. if the last
522        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
523        characters but of course it shouldn't be taken as a newline when it is part
524        of another character. The bug was that, for an unlimited repeat of . in
525        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
526        characters when looking for a newline.
528     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
530     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
531        in debug output.
533     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
534        long printing in the pcrecpp unittest when running under MinGW.
536     6. ESC_K was left out of the EBCDIC table.
538     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
539        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
540        limit also applies to "virtual nesting" when a pattern is recursive, and in
541        this case 1000 isn't so big. I have been able to remove this limit at the
542        expense of backing off one optimization in certain circumstances. Normally,
543        when pcre_exec() would call its internal match() function recursively and
544        immediately return the result unconditionally, it uses a "tail recursion"
545        feature to save stack. However, when a subpattern that can match an empty
546        string has an unlimited repetition quantifier, it no longer makes this
547        optimization. That gives it a stack frame in which to save the data for
548        checking that an empty string has been matched. Previously this was taken
549        from the 1000-entry workspace that had been reserved. So now there is no
550        explicit limit, but more stack is used.
552     8. Applied Daniel's patches to solve problems with the import/export magic
553        syntax that is required for Windows, and which was going wrong for the
554        pcreposix and pcrecpp parts of the library. These were overlooked when this
555        problem was solved for the main library.
557     9. There were some crude static tests to avoid integer overflow when computing
558        the size of patterns that contain repeated groups with explicit upper
559        limits. As the maximum quantifier is 65535, the maximum group length was
560        set at 30,000 so that the product of these two numbers did not overflow a
561        32-bit integer. However, it turns out that people want to use groups that
562        are longer than 30,000 bytes (though not repeat them that many times).
563        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
564        made it possible to implement the integer overflow checks in a much more
565        dynamic way, which I have now done. The artificial limitation on group
566        length has been removed - we now have only the limit on the total length of
567        the compiled pattern, which depends on the LINK_SIZE setting.
569    10. Fixed a bug in the documentation for get/copy named substring when
570        duplicate names are permitted. If none of the named substrings are set, the
571        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
572        empty string.
574    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
575        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
576        because the ] is interpreted as the first data character and the
577        terminating ] is not found. PCRE has been made compatible with Perl in this
578        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
579        cause memory overwriting.
581    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
582        string has been matched (to stop an infinite loop). It was not recognizing
583        a conditional subpattern that could match an empty string if that
584        subpattern was within another subpattern. For example, it looped when
585        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
586        condition was not nested. This bug has been fixed.
588    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
589        past the start of the subject in the presence of bytes with the top bit
590        set, for example "\x8aBCD".
592    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
593        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
595    14. Optimized (?!) to (*FAIL).
597    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
598        This restricts code points to be within the range 0 to 0x10FFFF, excluding
599        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
600        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
601        does: it's just the validity check that is more restrictive.
603    16. Inserted checks for integer overflows during escape sequence (backslash)
604        processing, and also fixed erroneous offset values for syntax errors during
605        backslash processing.
607    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
608        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
610    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
611        caused an overrun.
613    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
614        something other than just ASCII characters) inside a group that had an
615        unlimited repeat caused a loop at compile time (while checking to see
616        whether the group could match an empty string).
618    20. Debugging a pattern containing \p or \P could cause a crash. For example,
619        [\P{Any}] did so. (Error in the code for printing property names.)
621    21. An orphan \E inside a character class could cause a crash.
623    22. A repeated capturing bracket such as (A)? could cause a wild memory
624        reference during compilation.
626    23. There are several functions in pcre_compile() that scan along a compiled
627        expression for various reasons (e.g. to see if it's fixed length for look
628        behind). There were bugs in these functions when a repeated \p or \P was
629        present in the pattern. These operators have additional parameters compared
630        with \d, etc, and these were not being taken into account when moving along
631        the compiled data. Specifically:
633        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
634            length.
636        (b) An item such as \pL+ within a repeated group could cause crashes or
637            loops.
639        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
640            "reference to non-existent subpattern" error.
642        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
644    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
645        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
647    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
649    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
650        character were causing crashes (broken optimization).
652    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
653        \p or \P) caused a compile-time loop.
655    28. More problems have arisen in unanchored patterns when CRLF is a valid line
656        break. For example, the unstudied pattern [\r\n]A does not match the string
657        "\r\nA" because change 7.0/46 below moves the current point on by two
658        characters after failing to match at the start. However, the pattern \nA
659        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
660        the same is true. There doesn't seem any very clean way out of this, but
661        what I have chosen to do makes the common cases work: PCRE now takes note
662        of whether there can be an explicit match for \r or \n anywhere in the
663        pattern, and if so, 7.0/46 no longer applies. As part of this change,
664        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
665        pattern has explicit CR or LF references.
667    29. Added (*CR) etc for changing newline setting at start of pattern.
670    Version 7.2 19-Jun-07
671  ---------------------  ---------------------
673   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,   1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
# Line 40  Version 7.2 05-June-07 Line 706  Version 7.2 05-June-07
707      (f) \g{name} is another synonym - part of Perl 5.10's unification of      (f) \g{name} is another synonym - part of Perl 5.10's unification of
708          reference syntax.          reference syntax.
710      (g) (?| introduces a group in which the numbering of parentheses in each      (g) (?| introduces a group in which the numbering of parentheses in each
711          alternative starts with the same number.          alternative starts with the same number.
713      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.      (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
715   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and   7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
# Line 59  Version 7.2 05-June-07 Line 725  Version 7.2 05-June-07
725      bit of new cunning has reduced the workspace needed for groups with      bit of new cunning has reduced the workspace needed for groups with
726      alternatives. The 1000-alternative test pattern now uses 12 bytes of      alternatives. The 1000-alternative test pattern now uses 12 bytes of
727      workspace instead of running out of the 4096 that are available.      workspace instead of running out of the 4096 that are available.
729  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.  10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
731  11. Applied patch from Google to remove an optimization that didn't quite work.  11. Applied patch from Google to remove an optimization that didn't quite work.
732      The report of the bug said:      The report of the bug said:
734        pcrecpp::RE("a*").FullMatch("aaa") matches, while        pcrecpp::RE("a*").FullMatch("aaa") matches, while
735        pcrecpp::RE("a*?").FullMatch("aaa") does not, and        pcrecpp::RE("a*?").FullMatch("aaa") does not, and
736        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.        pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
738    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
739        it matched the wrong number of bytes.
742  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07

Removed from v.179  
changed lines
  Added in v.388

  ViewVC Help
Powered by ViewVC 1.1.5