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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.155  
changed lines
  Added in v.336

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12