/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.161  
changed lines
  Added in v.358

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12