ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 206 by ph10, Fri Aug 3 14:53:04 2007 UTC revision 396 by ph10, Fri Mar 20 11:23:20 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.3 05-Jul-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.
58    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
60    16. Added comments and documentation about mis-use of no_arg in the C++
61        wrapper.
63    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
64        from Martin Jerabek that uses macro names for all relevant character and
65        string constants.
67    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
68        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
69        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
70        these, but not everybody uses configure.
72    19. A conditional group that had only one branch was not being correctly
73        recognized as an item that could match an empty string. This meant that an
74        enclosing group might also not be so recognized, causing infinite looping
75        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
76        with the subject "ab", where knowledge that the repeated group can match
77        nothing is needed in order to break the loop.
80    Version 7.8 05-Sep-08
81    ---------------------
83    1.  Replaced UCP searching code with optimized version as implemented for Ad
84        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
85        stage table and inline lookup instead of a function, giving speed ups of 2
86        to 5 times on some simple patterns that I tested. Permission was given to
87        distribute the MultiStage2.py script that generates the tables (it's not in
88        the tarball, but is in the Subversion repository).
90    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
91        scripts.
93    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
94        a group with a zero qualifier. The result of the study could be incorrect,
95        or the function might crash, depending on the pattern.
97    4.  Caseless matching was not working for non-ASCII characters in back
98        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
99        It now works when Unicode Property Support is available.
101    5.  In pcretest, an escape such as \x{de} in the data was always generating
102        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
103        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
104        truncation.
106    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
108    7.  Added two (int) casts to pcregrep when printing the difference of two
109        pointers, in case they are 64-bit values.
111    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
112        test 2 if it fails.
114    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
115        and a #define of that name to empty if it is not externally set. This is to
116        allow users of MSVC to set it if necessary.
118    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
119        the convenience functions in the pcre_get.c source file.
121    11. An option change at the start of a pattern that had top-level alternatives
122        could cause overwriting and/or a crash. This command provoked a crash in
123        some environments:
125          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
127        This potential security problem was recorded as CVE-2008-2371.
129    12. For a pattern where the match had to start at the beginning or immediately
130        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
131        pcre_dfa_exec() could read past the end of the passed subject if there was
132        no match. To help with detecting such bugs (e.g. with valgrind), I modified
133        pcretest so that it places the subject at the end of its malloc-ed buffer.
135    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
136        exec() might read past the end of the data buffer in UTF-8 mode.
138    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
139        the data contained the byte 0x85 as part of a UTF-8 character within its
140        first line. This applied both to normal and DFA matching.
142    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
143        /^[^d]*?$/8 failed to match "abc".
145    16. Added a missing copyright notice to pcrecpp_internal.h.
147    17. Make it more clear in the documentation that values returned from
148        pcre_exec() in ovector are byte offsets, not character counts.
150    18. Tidied a few places to stop certain compilers from issuing warnings.
152    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
153        supplied by Stefan Weber. I made a further small update for 7.8 because
154        there is a change of source arrangements: the pcre_searchfuncs.c module is
155        replaced by pcre_ucd.c.
158    Version 7.7 07-May-08
159    ---------------------
161    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
162        a string to a long long, pretend we don't even have a long long." This is
163        done by checking for the strtoq, strtoll, and _strtoi64 functions.
165    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
166        pre-7.6 versions, which defined a global no_arg variable instead of putting
167        it in the RE class. (See also #8 below.)
169    3.  Remove a line of dead code, identified by coverity and reported by Nuno
170        Lopes.
172    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
174        (1) The include/exclude patterns were being applied to the whole pathnames
175            of files, instead of just to the final components.
177        (2) If there was more than one level of directory, the subdirectories were
178            skipped unless they satisfied the include/exclude conditions. This is
179            inconsistent with GNU grep (and could even be seen as contrary to the
180            pcregrep specification - which I improved to make it absolutely clear).
181            The action now is always to scan all levels of directory, and just
182            apply the include/exclude patterns to regular files.
184    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
185        --exclude_dir in the tests to avoid scanning .svn directories.
187    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
188        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
189        doesn't support NULs in patterns.
191    7.  Added some missing "const"s to declarations of static tables in
192        pcre_compile.c and pcre_dfa_exec.c.
194    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
195        caused by fix #2  above. (Subsequently also a second patch to fix the
196        first patch. And a third patch - this was a messy problem.)
198    9.  Applied Craig's patch to remove the use of push_back().
200    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
201        matching function regexec().
203    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
204        which, however, unlike Perl's \g{...}, are subroutine calls, not back
205        references. PCRE supports relative numbers with this syntax (I don't think
206        Oniguruma does).
208    12. Previously, a group with a zero repeat such as (...){0} was completely
209        omitted from the compiled regex. However, this means that if the group
210        was called as a subroutine from elsewhere in the pattern, things went wrong
211        (an internal error was given). Such groups are now left in the compiled
212        pattern, with a new opcode that causes them to be skipped at execution
213        time.
215    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
216        to the way PCRE behaves:
218        (a) A lone ] character is dis-allowed (Perl treats it as data).
220        (b) A back reference to an unmatched subpattern matches an empty string
221            (Perl fails the current match path).
223        (c) A data ] in a character class must be notated as \] because if the
224            first data character in a class is ], it defines an empty class. (In
225            Perl it is not possible to have an empty class.) The empty class []
226            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
227            The negative empty class [^] matches any one character, independently
228            of the DOTALL setting.
230    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
231        non-existent subpattern following a character class starting with ']' and
232        containing () gave an internal compiling error instead of "reference to
233        non-existent subpattern". Fortunately, when the pattern did exist, the
234        compiled code was correct. (When scanning forwards to check for the
235        existencd of the subpattern, it was treating the data ']' as terminating
236        the class, so got the count wrong. When actually compiling, the reference
237        was subsequently set up correctly.)
239    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
240        it was being rejected as not supported by pcre_dfa_exec(), even though
241        other assertions are supported. I have made pcre_dfa_exec() support
242        (*FAIL).
244    16. The implementation of 13c above involved the invention of a new opcode,
245        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
246        cannot be changed at match time, I realized I could make a small
247        improvement to matching performance by compiling OP_ALLANY instead of
248        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
249        on the OP_ANY path.
251    17. Compiling pcretest on Windows with readline support failed without the
252        following two fixes: (1) Make the unistd.h include conditional on
253        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
255    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
256        ncurses library to be included for pcretest when ReadLine support is
257        requested, but also to allow for it to be overridden. This patch came from
258        Daniel Bergström.
260    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
261        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
262        any errors with the current Unicode tables. Thanks to Peter Kankowski for
263        spotting this.
266    Version 7.6 28-Jan-08
267    ---------------------
269    1.  A character class containing a very large number of characters with
270        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
271        overflow.
273    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
274        HAVE_LONG_LONG is not defined.
276    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
277        bring them up to date and include new features. This patch includes:
279        - Fixed PH's badly added libz and libbz2 support.
280        - Fixed a problem with static linking.
281        - Added pcredemo. [But later removed - see 7 below.]
282        - Fixed dftables problem and added an option.
283        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
284            HAVE_LONG_LONG.
285        - Added readline support for pcretest.
286        - Added an listing of the option settings after cmake has run.
288    4.  A user submitted a patch to Makefile that makes it easy to create
289        "pcre.dll" under mingw when using Configure/Make. I added stuff to
290        Makefile.am that cause it to include this special target, without
291        affecting anything else. Note that the same mingw target plus all
292        the other distribution libraries and programs are now supported
293        when configuring with CMake (see 6 below) instead of with
294        Configure/Make.
296    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
297        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
298        exported in the Windows port". It has not yet been confirmed that the patch
299        solves the problem, but it does no harm.
301    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
302        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
303        with CMake, and also correct the comment about stack recursion.
305    7.  Remove the automatic building of pcredemo from the ./configure system and
306        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
307        of a program that users should build themselves after PCRE is installed, so
308        building it automatically is not really right. What is more, it gave
309        trouble in some build environments.
311    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
314    Version 7.5 10-Jan-08
315    ---------------------
317    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
318        values in parens when parsing an RE using the C++ wrapper."
320    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
321        Characters greater than 255 were excluded from the class instead of being
322        included.
324    3.  The same bug as (2) above applied to negated POSIX classes such as
325        [:^space:].
327    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
328        defined or documented. It seems to have been a typo for PCRE_STATIC, so
329        I have changed it.
331    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
332        first named subpattern) and a construct such as (?&a) would reference the
333        first named subpattern whose name started with "a" (in other words, the
334        length check was missing). Both these problems are fixed. "Subpattern name
335        expected" is now given for (?&) (a zero-length name), and this patch also
336        makes it give the same error for \k'' (previously it complained that that
337        was a reference to a non-existent subpattern).
339    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
340        this is right because (?- can be followed by option settings as well as by
341        digits. I have, however, made the messages clearer.
343    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
344        than the number used in the conditional) now cause a compile-time error.
345        This is actually not compatible with Perl, which accepts such patterns, but
346        treats the conditional as always being FALSE (as PCRE used to), but it
347        seems to me that giving a diagnostic is better.
349    8.  Change "alphameric" to the more common word "alphanumeric" in comments
350        and messages.
352    9.  Fix two occurrences of "backslash" in comments that should have been
353        "backspace".
355    10. Remove two redundant lines of code that can never be obeyed (their function
356        was moved elsewhere).
358    11. The program that makes PCRE's Unicode character property table had a bug
359        which caused it to generate incorrect table entries for sequences of
360        characters that have the same character type, but are in different scripts.
361        It amalgamated them into a single range, with the script of the first of
362        them. In other words, some characters were in the wrong script. There were
363        thirteen such cases, affecting characters in the following ranges:
365          U+002b0 - U+002c1
366          U+0060c - U+0060d
367          U+0061e - U+00612
368          U+0064b - U+0065e
369          U+0074d - U+0076d
370          U+01800 - U+01805
371          U+01d00 - U+01d77
372          U+01d9b - U+01dbf
373          U+0200b - U+0200f
374          U+030fc - U+030fe
375          U+03260 - U+0327f
376          U+0fb46 - U+0fbb1
377          U+10450 - U+1049d
379    12. The -o option (show only the matching part of a line) for pcregrep was not
380        compatible with GNU grep in that, if there was more than one match in a
381        line, it showed only the first of them. It now behaves in the same way as
382        GNU grep.
384    13. If the -o and -v options were combined for pcregrep, it printed a blank
385        line for every non-matching line. GNU grep prints nothing, and pcregrep now
386        does the same. The return code can be used to tell if there were any
387        non-matching lines.
389    14. Added --file-offsets and --line-offsets to pcregrep.
391    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
392        infinitely looping recursion. The bug was that positive lookaheads were not
393        being skipped when checking for a possible empty match (negative lookaheads
394        and both kinds of lookbehind were skipped).
396    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
397        inclusion of <windows.h> to before rather than after the definition of
398        INVALID_FILE_ATTRIBUTES (patch from David Byron).
400    17. Specifying a possessive quantifier with a specific limit for a Unicode
401        character property caused pcre_compile() to compile bad code, which led at
402        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
403        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
404        caused the error; without that there was no problem.
406    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
408    19. Added --enable-pcretest-libreadline.
410    20. In pcrecpp.cc, the variable 'count' was incremented twice in
411        RE::GlobalReplace(). As a result, the number of replacements returned was
412        double what it should be. I removed one of the increments, but Craig sent a
413        later patch that removed the other one (the right fix) and added unit tests
414        that check the return values (which was not done before).
416    21. Several CMake things:
418        (1) Arranged that, when cmake is used on Unix, the libraries end up with
419            the names libpcre and libpcreposix, not just pcre and pcreposix.
421        (2) The above change means that pcretest and pcregrep are now correctly
422            linked with the newly-built libraries, not previously installed ones.
426    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
427        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
428        UTF-8 newline character). The key issue is that the pattern starts .*;
429        this means that the match must be either at the beginning, or after a
430        newline. The bug was in the code for advancing after a failed match and
431        checking that the new position followed a newline. It was not taking
432        account of UTF-8 characters correctly.
434    23. PCRE was behaving differently from Perl in the way it recognized POSIX
435        character classes. PCRE was not treating the sequence [:...:] as a
436        character class unless the ... were all letters. Perl, however, seems to
437        allow any characters between [: and :], though of course it rejects as
438        unknown any "names" that contain non-letters, because all the known class
439        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
440        for example, whereas PCRE did not - it did not recognize a POSIX character
441        class. This seemed a bit dangerous, so the code has been changed to be
442        closer to Perl. The behaviour is not identical to Perl, because PCRE will
443        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
444        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
445        Perl does, and where it didn't before.
447    24. Rewrite so as to remove the single use of %n from pcregrep because in some
448        Windows environments %n is disabled by default.
451    Version 7.4 21-Sep-07
452    ---------------------
454    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
455        means that a class such as [\s] counted as "explicit reference to CR or
456        LF". That isn't really right - the whole point of the change was to try to
457        help when there was an actual mention of one of the two characters. So now
458        the change happens only if \r or \n (or a literal CR or LF) character is
459        encountered.
461    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
462        of both had grown to the point where there were only 3 bits left.
463        Fortunately, there was spare space in the data structure, and so I have
464        moved the internal flags into a new 16-bit field to free up more option
465        bits.
467    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
468        but did not set the internal JCHANGED flag - either of these is enough to
469        control the way the "get" function works - but the PCRE_INFO_JCHANGED
470        facility is supposed to tell if (?J) was ever used, so now (?J) at the
471        start sets both bits.
473    4.  Added options (at build time, compile time, exec time) to change \R from
474        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
476    5.  doc/pcresyntax.html was missing from the distribution.
478    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
479        compatibility, even though it is no longer used.
481    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
482        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
483        windows.h file is present (where different names are used). [This was
484        reversed later after testing - see 16 below.]
486    8.  Changed all #include <config.h> to #include "config.h". There were also
487        some further <pcre.h> cases that I changed to "pcre.h".
489    9.  When pcregrep was used with the --colour option, it missed the line ending
490        sequence off the lines that it output.
492    10. It was pointed out to me that arrays of string pointers cause lots of
493        relocations when a shared library is dynamically loaded. A technique of
494        using a single long string with a table of offsets can drastically reduce
495        these. I have refactored PCRE in four places to do this. The result is
496        dramatic:
498          Originally:                          290
499          After changing UCP table:            187
500          After changing error message table:   43
501          After changing table of "verbs"       36
502          After changing table of Posix names   22
504        Thanks to the folks working on Gregex for glib for this insight.
506    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
507        unicode-properties was also set.
509    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
511    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
512        checked only for CRLF.
514    14. Added casts to pcretest.c to avoid compiler warnings.
516    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
518    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
519        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
520        entirely. This removes changes made in 7 above.
522    17. The CMake files have been updated, and there is now more information about
523        building with CMake in the NON-UNIX-USE document.
526    Version 7.3 28-Aug-07
527  ---------------------  ---------------------
529   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 64  Version 7.3 05-Jul-07 Line 586  Version 7.3 05-Jul-07
586      dynamic way, which I have now done. The artificial limitation on group      dynamic way, which I have now done. The artificial limitation on group
587      length has been removed - we now have only the limit on the total length of      length has been removed - we now have only the limit on the total length of
588      the compiled pattern, which depends on the LINK_SIZE setting.      the compiled pattern, which depends on the LINK_SIZE setting.
590  10. Fixed a bug in the documentation for get/copy named substring when  10. Fixed a bug in the documentation for get/copy named substring when
591      duplicate names are permitted. If none of the named substrings are set, the      duplicate names are permitted. If none of the named substrings are set, the
592      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an      functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
593      empty string.      empty string.
595  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E  11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
596      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,      instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
597      because the ] is interpreted as the first data character and the      because the ] is interpreted as the first data character and the
598      terminating ] is not found. PCRE has been made compatible with Perl in this      terminating ] is not found. PCRE has been made compatible with Perl in this
599      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could      regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
600      cause memory overwriting.      cause memory overwriting.
602  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty  10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
603      string has been matched (to stop an infinite loop). It was not recognizing      string has been matched (to stop an infinite loop). It was not recognizing
604      a conditional subpattern that could match an empty string if that      a conditional subpattern that could match an empty string if that
605      subpattern was within another subpattern. For example, it looped when      subpattern was within another subpattern. For example, it looped when
606      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the      trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
607      condition was not nested. This bug has been fixed.      condition was not nested. This bug has been fixed.
609    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
610        past the start of the subject in the presence of bytes with the top bit
611        set, for example "\x8aBCD".
613    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
614        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
616    14. Optimized (?!) to (*FAIL).
618    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
619        This restricts code points to be within the range 0 to 0x10FFFF, excluding
620        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
621        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
622        does: it's just the validity check that is more restrictive.
624    16. Inserted checks for integer overflows during escape sequence (backslash)
625        processing, and also fixed erroneous offset values for syntax errors during
626        backslash processing.
628    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
629        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
631    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
632        caused an overrun.
634    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
635        something other than just ASCII characters) inside a group that had an
636        unlimited repeat caused a loop at compile time (while checking to see
637        whether the group could match an empty string).
639    20. Debugging a pattern containing \p or \P could cause a crash. For example,
640        [\P{Any}] did so. (Error in the code for printing property names.)
642    21. An orphan \E inside a character class could cause a crash.
644    22. A repeated capturing bracket such as (A)? could cause a wild memory
645        reference during compilation.
647    23. There are several functions in pcre_compile() that scan along a compiled
648        expression for various reasons (e.g. to see if it's fixed length for look
649        behind). There were bugs in these functions when a repeated \p or \P was
650        present in the pattern. These operators have additional parameters compared
651        with \d, etc, and these were not being taken into account when moving along
652        the compiled data. Specifically:
654        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
655            length.
657        (b) An item such as \pL+ within a repeated group could cause crashes or
658            loops.
660        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
661            "reference to non-existent subpattern" error.
663        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
665    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
666        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
668    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
670    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
671        character were causing crashes (broken optimization).
673    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
674        \p or \P) caused a compile-time loop.
676    28. More problems have arisen in unanchored patterns when CRLF is a valid line
677        break. For example, the unstudied pattern [\r\n]A does not match the string
678        "\r\nA" because change 7.0/46 below moves the current point on by two
679        characters after failing to match at the start. However, the pattern \nA
680        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
681        the same is true. There doesn't seem any very clean way out of this, but
682        what I have chosen to do makes the common cases work: PCRE now takes note
683        of whether there can be an explicit match for \r or \n anywhere in the
684        pattern, and if so, 7.0/46 no longer applies. As part of this change,
685        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
686        pattern has explicit CR or LF references.
688    29. Added (*CR) etc for changing newline setting at start of pattern.
691  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07
692  ---------------------  ---------------------

Removed from v.206  
changed lines
  Added in v.396

  ViewVC Help
Powered by ViewVC 1.1.5