ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.205  
changed lines
  Added in v.376

  ViewVC Help
Powered by ViewVC 1.1.5