ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.153  
changed lines
  Added in v.340

  ViewVC Help
Powered by ViewVC 1.1.5