ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 164 by ph10, Fri May 4 15:11:14 2007 UTC revision 361 by ph10, Thu Jul 10 16:03:28 2008 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.2 01-May-07  Version 8.0 02 Jul-08
5    ---------------------
7    1.  Replaced UCP searching code with optimized version as implemented for Ad
8        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
9        stage table and inline lookup instead of a function, giving speed ups of 2
10        to 5 times on some simple patterns that I tested. Permission was given to
11        distribute the MultiStage2.py script that generates the tables (it's not in
12        the tarball, but is in the Subversion repository).
14    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
15        scripts.
17    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
18        a group with a zero qualifier. The result of the study could be incorrect,
19        or the function might crash, depending on the pattern.
21    4.  Caseless matching was not working for non-ASCII characters in back
22        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
23        It now works when Unicode Property Support is available.
25    5.  In pcretest, an escape such as \x{de} in the data was always generating
26        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
27        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
28        truncation.
30    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
32    7.  Added two (int) casts to pcregrep when printing the difference of two
33        pointers, in case they are 64-bit values.
35    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
36        test 2 if it fails.
38    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
39        and a #define of that name to empty if it is not externally set. This is to
40        allow users of MSVC to set it if necessary.
42    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
43        the convenience functions in the pcre_get.c source file.
45    11. An option change at the start of a pattern that had top-level alternatives
46        could cause overwriting and/or a crash. This command provoked a crash in
47        some environments:
49          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
51        This potential security problem was recorded as CVE-2008-2371.
53    12. For a pattern where the match had to start at the beginning or immediately
54        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
55        pcre_dfa_exec() could read past the end of the passed subject if there was
56        no match. To help with detecting such bugs (e.g. with valgrind), I modified
57        pcretest so that it places the subject at the end of its malloc-ed buffer.
60    Version 7.7 07-May-08
61    ---------------------
63    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
64        a string to a long long, pretend we don't even have a long long." This is
65        done by checking for the strtoq, strtoll, and _strtoi64 functions.
67    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
68        pre-7.6 versions, which defined a global no_arg variable instead of putting
69        it in the RE class. (See also #8 below.)
71    3.  Remove a line of dead code, identified by coverity and reported by Nuno
72        Lopes.
74    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
76        (1) The include/exclude patterns were being applied to the whole pathnames
77            of files, instead of just to the final components.
79        (2) If there was more than one level of directory, the subdirectories were
80            skipped unless they satisfied the include/exclude conditions. This is
81            inconsistent with GNU grep (and could even be seen as contrary to the
82            pcregrep specification - which I improved to make it absolutely clear).
83            The action now is always to scan all levels of directory, and just
84            apply the include/exclude patterns to regular files.
86    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
87        --exclude_dir in the tests to avoid scanning .svn directories.
89    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
90        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
91        doesn't support NULs in patterns.
93    7.  Added some missing "const"s to declarations of static tables in
94        pcre_compile.c and pcre_dfa_exec.c.
96    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
97        caused by fix #2  above. (Subsequently also a second patch to fix the
98        first patch. And a third patch - this was a messy problem.)
100    9.  Applied Craig's patch to remove the use of push_back().
102    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
103        matching function regexec().
105    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
106        which, however, unlike Perl's \g{...}, are subroutine calls, not back
107        references. PCRE supports relative numbers with this syntax (I don't think
108        Oniguruma does).
110    12. Previously, a group with a zero repeat such as (...){0} was completely
111        omitted from the compiled regex. However, this means that if the group
112        was called as a subroutine from elsewhere in the pattern, things went wrong
113        (an internal error was given). Such groups are now left in the compiled
114        pattern, with a new opcode that causes them to be skipped at execution
115        time.
117    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
118        to the way PCRE behaves:
120        (a) A lone ] character is dis-allowed (Perl treats it as data).
122        (b) A back reference to an unmatched subpattern matches an empty string
123            (Perl fails the current match path).
125        (c) A data ] in a character class must be notated as \] because if the
126            first data character in a class is ], it defines an empty class. (In
127            Perl it is not possible to have an empty class.) The empty class []
128            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
129            The negative empty class [^] matches any one character, independently
130            of the DOTALL setting.
132    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
133        non-existent subpattern following a character class starting with ']' and
134        containing () gave an internal compiling error instead of "reference to
135        non-existent subpattern". Fortunately, when the pattern did exist, the
136        compiled code was correct. (When scanning forwards to check for the
137        existencd of the subpattern, it was treating the data ']' as terminating
138        the class, so got the count wrong. When actually compiling, the reference
139        was subsequently set up correctly.)
141    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
142        it was being rejected as not supported by pcre_dfa_exec(), even though
143        other assertions are supported. I have made pcre_dfa_exec() support
144        (*FAIL).
146    16. The implementation of 13c above involved the invention of a new opcode,
147        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
148        cannot be changed at match time, I realized I could make a small
149        improvement to matching performance by compiling OP_ALLANY instead of
150        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
151        on the OP_ANY path.
153    17. Compiling pcretest on Windows with readline support failed without the
154        following two fixes: (1) Make the unistd.h include conditional on
155        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
157    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
158        ncurses library to be included for pcretest when ReadLine support is
159        requested, but also to allow for it to be overridden. This patch came from
160        Daniel Bergström.
162    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
163        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
164        any errors with the current Unicode tables. Thanks to Peter Kankowski for
165        spotting this.
168    Version 7.6 28-Jan-08
169    ---------------------
171    1.  A character class containing a very large number of characters with
172        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
173        overflow.
175    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
176        HAVE_LONG_LONG is not defined.
178    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
179        bring them up to date and include new features. This patch includes:
181        - Fixed PH's badly added libz and libbz2 support.
182        - Fixed a problem with static linking.
183        - Added pcredemo. [But later removed - see 7 below.]
184        - Fixed dftables problem and added an option.
185        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
186            HAVE_LONG_LONG.
187        - Added readline support for pcretest.
188        - Added an listing of the option settings after cmake has run.
190    4.  A user submitted a patch to Makefile that makes it easy to create
191        "pcre.dll" under mingw when using Configure/Make. I added stuff to
192        Makefile.am that cause it to include this special target, without
193        affecting anything else. Note that the same mingw target plus all
194        the other distribution libraries and programs are now supported
195        when configuring with CMake (see 6 below) instead of with
196        Configure/Make.
198    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
199        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
200        exported in the Windows port". It has not yet been confirmed that the patch
201        solves the problem, but it does no harm.
203    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
204        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
205        with CMake, and also correct the comment about stack recursion.
207    7.  Remove the automatic building of pcredemo from the ./configure system and
208        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
209        of a program that users should build themselves after PCRE is installed, so
210        building it automatically is not really right. What is more, it gave
211        trouble in some build environments.
213    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
216    Version 7.5 10-Jan-08
217    ---------------------
219    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
220        values in parens when parsing an RE using the C++ wrapper."
222    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
223        Characters greater than 255 were excluded from the class instead of being
224        included.
226    3.  The same bug as (2) above applied to negated POSIX classes such as
227        [:^space:].
229    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
230        defined or documented. It seems to have been a typo for PCRE_STATIC, so
231        I have changed it.
233    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
234        first named subpattern) and a construct such as (?&a) would reference the
235        first named subpattern whose name started with "a" (in other words, the
236        length check was missing). Both these problems are fixed. "Subpattern name
237        expected" is now given for (?&) (a zero-length name), and this patch also
238        makes it give the same error for \k'' (previously it complained that that
239        was a reference to a non-existent subpattern).
241    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
242        this is right because (?- can be followed by option settings as well as by
243        digits. I have, however, made the messages clearer.
245    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
246        than the number used in the conditional) now cause a compile-time error.
247        This is actually not compatible with Perl, which accepts such patterns, but
248        treats the conditional as always being FALSE (as PCRE used to), but it
249        seems to me that giving a diagnostic is better.
251    8.  Change "alphameric" to the more common word "alphanumeric" in comments
252        and messages.
254    9.  Fix two occurrences of "backslash" in comments that should have been
255        "backspace".
257    10. Remove two redundant lines of code that can never be obeyed (their function
258        was moved elsewhere).
260    11. The program that makes PCRE's Unicode character property table had a bug
261        which caused it to generate incorrect table entries for sequences of
262        characters that have the same character type, but are in different scripts.
263        It amalgamated them into a single range, with the script of the first of
264        them. In other words, some characters were in the wrong script. There were
265        thirteen such cases, affecting characters in the following ranges:
267          U+002b0 - U+002c1
268          U+0060c - U+0060d
269          U+0061e - U+00612
270          U+0064b - U+0065e
271          U+0074d - U+0076d
272          U+01800 - U+01805
273          U+01d00 - U+01d77
274          U+01d9b - U+01dbf
275          U+0200b - U+0200f
276          U+030fc - U+030fe
277          U+03260 - U+0327f
278          U+0fb46 - U+0fbb1
279          U+10450 - U+1049d
281    12. The -o option (show only the matching part of a line) for pcregrep was not
282        compatible with GNU grep in that, if there was more than one match in a
283        line, it showed only the first of them. It now behaves in the same way as
284        GNU grep.
286    13. If the -o and -v options were combined for pcregrep, it printed a blank
287        line for every non-matching line. GNU grep prints nothing, and pcregrep now
288        does the same. The return code can be used to tell if there were any
289        non-matching lines.
291    14. Added --file-offsets and --line-offsets to pcregrep.
293    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
294        infinitely looping recursion. The bug was that positive lookaheads were not
295        being skipped when checking for a possible empty match (negative lookaheads
296        and both kinds of lookbehind were skipped).
298    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
299        inclusion of <windows.h> to before rather than after the definition of
300        INVALID_FILE_ATTRIBUTES (patch from David Byron).
302    17. Specifying a possessive quantifier with a specific limit for a Unicode
303        character property caused pcre_compile() to compile bad code, which led at
304        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
305        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
306        caused the error; without that there was no problem.
308    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
310    19. Added --enable-pcretest-libreadline.
312    20. In pcrecpp.cc, the variable 'count' was incremented twice in
313        RE::GlobalReplace(). As a result, the number of replacements returned was
314        double what it should be. I removed one of the increments, but Craig sent a
315        later patch that removed the other one (the right fix) and added unit tests
316        that check the return values (which was not done before).
318    21. Several CMake things:
320        (1) Arranged that, when cmake is used on Unix, the libraries end up with
321            the names libpcre and libpcreposix, not just pcre and pcreposix.
323        (2) The above change means that pcretest and pcregrep are now correctly
324            linked with the newly-built libraries, not previously installed ones.
328    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
329        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
330        UTF-8 newline character). The key issue is that the pattern starts .*;
331        this means that the match must be either at the beginning, or after a
332        newline. The bug was in the code for advancing after a failed match and
333        checking that the new position followed a newline. It was not taking
334        account of UTF-8 characters correctly.
336    23. PCRE was behaving differently from Perl in the way it recognized POSIX
337        character classes. PCRE was not treating the sequence [:...:] as a
338        character class unless the ... were all letters. Perl, however, seems to
339        allow any characters between [: and :], though of course it rejects as
340        unknown any "names" that contain non-letters, because all the known class
341        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
342        for example, whereas PCRE did not - it did not recognize a POSIX character
343        class. This seemed a bit dangerous, so the code has been changed to be
344        closer to Perl. The behaviour is not identical to Perl, because PCRE will
345        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
346        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
347        Perl does, and where it didn't before.
349    24. Rewrite so as to remove the single use of %n from pcregrep because in some
350        Windows environments %n is disabled by default.
353    Version 7.4 21-Sep-07
354    ---------------------
356    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
357        means that a class such as [\s] counted as "explicit reference to CR or
358        LF". That isn't really right - the whole point of the change was to try to
359        help when there was an actual mention of one of the two characters. So now
360        the change happens only if \r or \n (or a literal CR or LF) character is
361        encountered.
363    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
364        of both had grown to the point where there were only 3 bits left.
365        Fortunately, there was spare space in the data structure, and so I have
366        moved the internal flags into a new 16-bit field to free up more option
367        bits.
369    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
370        but did not set the internal JCHANGED flag - either of these is enough to
371        control the way the "get" function works - but the PCRE_INFO_JCHANGED
372        facility is supposed to tell if (?J) was ever used, so now (?J) at the
373        start sets both bits.
375    4.  Added options (at build time, compile time, exec time) to change \R from
376        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
378    5.  doc/pcresyntax.html was missing from the distribution.
380    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
381        compatibility, even though it is no longer used.
383    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
384        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
385        windows.h file is present (where different names are used). [This was
386        reversed later after testing - see 16 below.]
388    8.  Changed all #include <config.h> to #include "config.h". There were also
389        some further <pcre.h> cases that I changed to "pcre.h".
391    9.  When pcregrep was used with the --colour option, it missed the line ending
392        sequence off the lines that it output.
394    10. It was pointed out to me that arrays of string pointers cause lots of
395        relocations when a shared library is dynamically loaded. A technique of
396        using a single long string with a table of offsets can drastically reduce
397        these. I have refactored PCRE in four places to do this. The result is
398        dramatic:
400          Originally:                          290
401          After changing UCP table:            187
402          After changing error message table:   43
403          After changing table of "verbs"       36
404          After changing table of Posix names   22
406        Thanks to the folks working on Gregex for glib for this insight.
408    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
409        unicode-properties was also set.
411    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
413    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
414        checked only for CRLF.
416    14. Added casts to pcretest.c to avoid compiler warnings.
418    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
420    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
421        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
422        entirely. This removes changes made in 7 above.
424    17. The CMake files have been updated, and there is now more information about
425        building with CMake in the NON-UNIX-USE document.
428    Version 7.3 28-Aug-07
429    ---------------------
431     1. In the rejigging of the build system that eventually resulted in 7.1, the
432        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
433        brackets there is not right, since it causes compilers to look for an
434        installed pcre.h, not the version that is in the source that is being
435        compiled (which of course may be different). I have changed it back to:
437          #include "pcre.h"
439        I have a vague recollection that the change was concerned with compiling in
440        different directories, but in the new build system, that is taken care of
441        by the VPATH setting the Makefile.
443     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
444        when the subject happened to end in the byte 0x85 (e.g. if the last
445        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
446        characters but of course it shouldn't be taken as a newline when it is part
447        of another character. The bug was that, for an unlimited repeat of . in
448        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
449        characters when looking for a newline.
451     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
453     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
454        in debug output.
456     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
457        long printing in the pcrecpp unittest when running under MinGW.
459     6. ESC_K was left out of the EBCDIC table.
461     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
462        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
463        limit also applies to "virtual nesting" when a pattern is recursive, and in
464        this case 1000 isn't so big. I have been able to remove this limit at the
465        expense of backing off one optimization in certain circumstances. Normally,
466        when pcre_exec() would call its internal match() function recursively and
467        immediately return the result unconditionally, it uses a "tail recursion"
468        feature to save stack. However, when a subpattern that can match an empty
469        string has an unlimited repetition quantifier, it no longer makes this
470        optimization. That gives it a stack frame in which to save the data for
471        checking that an empty string has been matched. Previously this was taken
472        from the 1000-entry workspace that had been reserved. So now there is no
473        explicit limit, but more stack is used.
475     8. Applied Daniel's patches to solve problems with the import/export magic
476        syntax that is required for Windows, and which was going wrong for the
477        pcreposix and pcrecpp parts of the library. These were overlooked when this
478        problem was solved for the main library.
480     9. There were some crude static tests to avoid integer overflow when computing
481        the size of patterns that contain repeated groups with explicit upper
482        limits. As the maximum quantifier is 65535, the maximum group length was
483        set at 30,000 so that the product of these two numbers did not overflow a
484        32-bit integer. However, it turns out that people want to use groups that
485        are longer than 30,000 bytes (though not repeat them that many times).
486        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
487        made it possible to implement the integer overflow checks in a much more
488        dynamic way, which I have now done. The artificial limitation on group
489        length has been removed - we now have only the limit on the total length of
490        the compiled pattern, which depends on the LINK_SIZE setting.
492    10. Fixed a bug in the documentation for get/copy named substring when
493        duplicate names are permitted. If none of the named substrings are set, the
494        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
495        empty string.
497    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
498        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
499        because the ] is interpreted as the first data character and the
500        terminating ] is not found. PCRE has been made compatible with Perl in this
501        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
502        cause memory overwriting.
504    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
505        string has been matched (to stop an infinite loop). It was not recognizing
506        a conditional subpattern that could match an empty string if that
507        subpattern was within another subpattern. For example, it looped when
508        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
509        condition was not nested. This bug has been fixed.
511    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
512        past the start of the subject in the presence of bytes with the top bit
513        set, for example "\x8aBCD".
515    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
516        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
518    14. Optimized (?!) to (*FAIL).
520    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
521        This restricts code points to be within the range 0 to 0x10FFFF, excluding
522        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
523        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
524        does: it's just the validity check that is more restrictive.
526    16. Inserted checks for integer overflows during escape sequence (backslash)
527        processing, and also fixed erroneous offset values for syntax errors during
528        backslash processing.
530    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
531        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
533    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
534        caused an overrun.
536    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
537        something other than just ASCII characters) inside a group that had an
538        unlimited repeat caused a loop at compile time (while checking to see
539        whether the group could match an empty string).
541    20. Debugging a pattern containing \p or \P could cause a crash. For example,
542        [\P{Any}] did so. (Error in the code for printing property names.)
544    21. An orphan \E inside a character class could cause a crash.
546    22. A repeated capturing bracket such as (A)? could cause a wild memory
547        reference during compilation.
549    23. There are several functions in pcre_compile() that scan along a compiled
550        expression for various reasons (e.g. to see if it's fixed length for look
551        behind). There were bugs in these functions when a repeated \p or \P was
552        present in the pattern. These operators have additional parameters compared
553        with \d, etc, and these were not being taken into account when moving along
554        the compiled data. Specifically:
556        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
557            length.
559        (b) An item such as \pL+ within a repeated group could cause crashes or
560            loops.
562        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
563            "reference to non-existent subpattern" error.
565        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
567    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
568        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
570    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
572    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
573        character were causing crashes (broken optimization).
575    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
576        \p or \P) caused a compile-time loop.
578    28. More problems have arisen in unanchored patterns when CRLF is a valid line
579        break. For example, the unstudied pattern [\r\n]A does not match the string
580        "\r\nA" because change 7.0/46 below moves the current point on by two
581        characters after failing to match at the start. However, the pattern \nA
582        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
583        the same is true. There doesn't seem any very clean way out of this, but
584        what I have chosen to do makes the common cases work: PCRE now takes note
585        of whether there can be an explicit match for \r or \n anywhere in the
586        pattern, and if so, 7.0/46 no longer applies. As part of this change,
587        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
588        pattern has explicit CR or LF references.
590    29. Added (*CR) etc for changing newline setting at start of pattern.
593    Version 7.2 19-Jun-07
594  ---------------------  ---------------------
596   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 11  Version 7.2 01-May-07 Line 600  Version 7.2 01-May-07
600      to make them independent of the local environment's newline setting.      to make them independent of the local environment's newline setting.
602   3. Add code to configure.ac to remove -g from the CFLAGS default settings.   3. Add code to configure.ac to remove -g from the CFLAGS default settings.
604   4. Some of the "internals" tests were previously cut out when the link size   4. Some of the "internals" tests were previously cut out when the link size
605      was not 2, because the output contained actual offsets. The recent new      was not 2, because the output contained actual offsets. The recent new
606      "Z" feature of pcretest means that these can be cut out, making the tests      "Z" feature of pcretest means that these can be cut out, making the tests
607      usable with all link sizes.      usable with all link sizes.
609   5. Implemented Stan Switzer's goto replacement for longjmp() when not using   5. Implemented Stan Switzer's goto replacement for longjmp() when not using
610      stack recursion. This gives a massive performance boost under BSD, but just      stack recursion. This gives a massive performance boost under BSD, but just
611      a small improvement under Linux. However, it saves one field in the frame      a small improvement under Linux. However, it saves one field in the frame
612      in all cases.      in all cases.
614     6. Added more features from the forthcoming Perl 5.10:
616        (a) (?-n) (where n is a string of digits) is a relative subroutine or
617            recursion call. It refers to the nth most recently opened parentheses.
619        (b) (?+n) is also a relative subroutine call; it refers to the nth next
620            to be opened parentheses.
622        (c) Conditions that refer to capturing parentheses can be specified
623            relatively, for example, (?(-2)... or (?(+3)...
625        (d) \K resets the start of the current match so that everything before
626            is not part of it.
628        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
630        (f) \g{name} is another synonym - part of Perl 5.10's unification of
631            reference syntax.
633        (g) (?| introduces a group in which the numbering of parentheses in each
634            alternative starts with the same number.
636        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
638     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
641     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
642        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
643        for detecting groups that can match an empty string.
645     9. A pattern with a very large number of alternatives (more than several
646        hundred) was running out of internal workspace during the pre-compile
647        phase, where pcre_compile() figures out how much memory will be needed. A
648        bit of new cunning has reduced the workspace needed for groups with
649        alternatives. The 1000-alternative test pattern now uses 12 bytes of
650        workspace instead of running out of the 4096 that are available.
652    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
654    11. Applied patch from Google to remove an optimization that didn't quite work.
655        The report of the bug said:
657          pcrecpp::RE("a*").FullMatch("aaa") matches, while
658          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
659          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
661    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
662        it matched the wrong number of bytes.
665  Version 7.1 24-Apr-07  Version 7.1 24-Apr-07
666  ---------------------  ---------------------

Removed from v.164  
changed lines
  Added in v.361

  ViewVC Help
Powered by ViewVC 1.1.5