ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 595 by ph10, Mon May 2 10:33:29 2011 UTC revision 914 by zherczeg, Mon Feb 13 06:04:50 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.13 30-Apr-2011  Version 8.31
5    -----------------------------
7    1.  Fixing a wrong JIT test case and some compiler warnings.
9    2.  Removed a bashism from the RunTest script.
11    3.  Add a cast to pcre_exec.c to fix the warning "unary minus operator applied
12        to unsigned type, result still unsigned" that was given by an MS compiler
13        on encountering the code "-sizeof(xxx)".
15    4.  Partial matching support is added to the JIT compiler.
18    Version 8.30 04-February-2012
19    -----------------------------
21    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
22        name is defined in ctype.h.
24    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
25        only in quite long subpatterns.
27    3.  Removed the function pcre_info(), which has been obsolete and deprecated
28        since it was replaced by pcre_fullinfo() in February 2000.
30    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
31        match a (*MARK), and the match failed at the start of the subject, a
32        reference to memory before the start of the subject could occur. This bug
33        was introduced by fix 17 of release 8.21.
35    5.  A reference to an unset group with zero minimum repetition was giving
36        totally wrong answers (in non-JavaScript-compatibility mode). For example,
37        /(another)?(\1?)test/ matched against "hello world test". This bug was
38        introduced in release 8.13.
40    6.  Add support for 16-bit character strings (a large amount of work involving
41        many changes and refactorings).
43    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
44        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
45        from a file.
47    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
48        rounding is not applied in this particular case).
50    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
51        if they appear, or are escaped, in patterns.
53    10. Get rid of a number of -Wunused-but-set-variable warnings.
55    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
56        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
57        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
58        also returns the mark "x". This bug applied to capturing parentheses,
59        non-capturing parentheses, and atomic parentheses. It also applied to some
60        assertions.
62    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
63        information out of configure.ac instead of relying on pcre.h.generic, which
64        is not stored in the repository.
66    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
67        -lreadline.
69    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
71    15. Applied Graycode's patch to put the top-level frame on the stack rather
72        than the heap when not using the stack for recursion. This gives a
73        performance improvement in many cases when recursion is not deep.
75    16. Experimental code added to "pcretest -C" to output the stack frame size.
78    Version 8.21 12-Dec-2011
79    ------------------------
81    1.  Updating the JIT compiler.
83    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
84        are added as well.
86    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
87        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
88        calling _pcre_jit_exec. Some extra comments are added.
90    4.  (*MARK) settings inside atomic groups that do not contain any capturing
91        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
92        was introduced by change 18 for 8.20.
94    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
95        ECMA-262 standard.
97    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
98        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
99        This bug was probably introduced by change 9 of 8.13.
101    7.  While fixing 6 above, I noticed that a number of other items were being
102        incorrectly rejected as "not fixed length". This arose partly because newer
103        opcodes had not been added to the fixed-length checking code. I have (a)
104        corrected the bug and added tests for these items, and (b) arranged for an
105        error to occur if an unknown opcode is encountered while checking for fixed
106        length instead of just assuming "not fixed length". The items that were
107        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
108        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
109        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
111    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
112        being incorrectly compiled and would have given unpredicatble results.
114    9.  A possessively repeated subpattern with minimum repeat count greater than
115        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
116        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
117        the first (A) could occur when it should not.
119    10. Add a cast and remove a redundant test from the code.
121    11. JIT should use pcre_malloc/pcre_free for allocation.
123    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
124        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
125        is anything other than /usr, -L is still shown).
127    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
129    14. Perl does not support \N without a following name in a [] class; PCRE now
130        also gives an error.
132    15. If a forward reference was repeated with an upper limit of around 2000,
133        it caused the error "internal error: overran compiling workspace". The
134        maximum number of forward references (including repeats) was limited by the
135        internal workspace, and dependent on the LINK_SIZE. The code has been
136        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
137        the default depends on LINK_SIZE. There is a new upper limit (for safety)
138        of around 200,000 forward references. While doing this, I also speeded up
139        the filling in of repeated forward references.
141    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
142        incorrectly expecting the subject to contain another "a" after the start.
144    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
145        in the match, the SKIP should be ignored. This was not happening; instead
146        the SKIP was being treated as NOMATCH. For patterns such as
147        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
148        tested.
150    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
151        now much more compatible with Perl, in particular in cases where the result
152        is a non-match for a non-anchored pattern. For example, if
153        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
154        "m", where previously it did not return a name. A side effect of this
155        change is that for partial matches, the last encountered mark name is
156        returned, as for non matches. A number of tests that were previously not
157        Perl-compatible have been moved into the Perl-compatible test files. The
158        refactoring has had the pleasing side effect of removing one argument from
159        the match() function, thus reducing its stack requirements.
161    19. If the /S+ option was used in pcretest to study a pattern using JIT,
162        subsequent uses of /S (without +) incorrectly behaved like /S+.
164    21. Retrieve executable code size support for the JIT compiler and fixing
165        some warnings.
167    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
168        not work when the shorter character appeared right at the end of the
169        subject string.
171    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
172        systems.
174    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
175        output it when the /M option is used in pcretest.
177    25. The CheckMan script was not being included in the distribution. Also, added
178        an explicit "perl" to run Perl scripts from the PrepareRelease script
179        because this is reportedly needed in Windows.
181    26. If study data was being save in a file and studying had not found a set of
182        "starts with" bytes for the pattern, the data written to the file (though
183        never used) was taken from uninitialized memory and so caused valgrind to
184        complain.
186    27. Updated RunTest.bat as provided by Sheri Pierce.
188    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
190    29. Computation of memory usage for the table of capturing group names was
191        giving an unnecessarily large value.
194    Version 8.20 21-Oct-2011
195    ------------------------
197    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
198        a POSIX class. After further experiments with Perl, which convinced me that
199        Perl has bugs and confusions, a closing square bracket is no longer allowed
200        in a POSIX name. This bug also affected patterns with classes that started
201        with full stops.
203    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
204        captured substring, but while checking the failing first alternative,
205        substring 1 is temporarily captured. If the output vector supplied to
206        pcre_exec() was not big enough for this capture, the yield of the function
207        was still zero ("insufficient space for captured substrings"). This cannot
208        be totally fixed without adding another stack variable, which seems a lot
209        of expense for a edge case. However, I have improved the situation in cases
210        such as /(a)(b)x|abc/ matched against "abc", where the return code
211        indicates that fewer than the maximum number of slots in the ovector have
212        been set.
214    3.  Related to (2) above: when there are more back references in a pattern than
215        slots in the output vector, pcre_exec() uses temporary memory during
216        matching, and copies in the captures as far as possible afterwards. It was
217        using the entire output vector, but this conflicts with the specification
218        that only 2/3 is used for passing back captured substrings. Now it uses
219        only the first 2/3, for compatibility. This is, of course, another edge
220        case.
222    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
223        main code base, and can be used by building with --enable-jit. When this is
224        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
225        runtime --no-jit option is given.
227    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
228        ovector, the return from the function was zero, implying that there were
229        other matches that did not fit. The correct "exactly full" value is now
230        returned.
232    6.  If a subpattern that was called recursively or as a subroutine contained
233        (*PRUNE) or any other control that caused it to give a non-standard return,
234        invalid errors such as "Error -26 (nested recursion at the same subject
235        position)" or even infinite loops could occur.
237    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
238        computing the minimum length on reaching *ACCEPT, and so ended up with the
239        wrong value of 1 rather than 0. Further investigation indicates that
240        computing a minimum subject length in the presence of *ACCEPT is difficult
241        (think back references, subroutine calls), and so I have changed the code
242        so that no minimum is registered for a pattern that contains *ACCEPT.
244    8.  If (*THEN) was present in the first (true) branch of a conditional group,
245        it was not handled as intended. [But see 16 below.]
247    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
248        Sheri Pierce.
250    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
251        the first byte in a match must be "a".
253    11. Change 17 for 8.13 increased the recursion depth for patterns like
254        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
255        pattern contains any instances of (*THEN). If it does not, the old
256        optimizations are restored. It would be nice to do this on a per-group
257        basis, but at the moment that is not feasible.
259    12. In some environments, the output of pcretest -C is CRLF terminated. This
260        broke RunTest's code that checks for the link size. A single white space
261        character after the value is now allowed for.
263    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
264        For "fr", it uses the Windows-specific input and output files.
266    14. If (*THEN) appeared in a group that was called recursively or as a
267        subroutine, it did not work as intended. [But see next item.]
269    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
270        pattern fragments (but not containing any | characters). If A and B are
271        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
272        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
273        D. In other words, Perl considers parentheses that do not contain any |
274        characters to be part of a surrounding alternative, whereas PCRE was
275        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
276        differently. PCRE now behaves in the same way as Perl, except in the case
277        of subroutine/recursion calls such as (?1) which have in any case always
278        been different (but PCRE had them first :-).
280    16. Related to 15 above: Perl does not treat the | in a conditional group as
281        creating alternatives. Such a group is treated in the same way as an
282        ordinary group without any | characters when processing (*THEN). PCRE has
283        been changed to match Perl's behaviour.
285    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
286        RunGrepTest script failed.
288    18. Change 22 for version 13 caused atomic groups to use more stack. This is
289        inevitable for groups that contain captures, but it can lead to a lot of
290        stack use in large patterns. The old behaviour has been restored for atomic
291        groups that do not contain any capturing parentheses.
293    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
294        suppress the check for a minimum subject length at run time. (If it was
295        given to pcre_exec() or pcre_dfa_exec() it did work.)
297    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
298        fail to work when decoding hex characters in data strings in EBCDIC
299        environments.
301    21. It appears that in at least one Mac OS environment, the isxdigit() function
302        is implemented as a macro that evaluates to its argument more than once,
303        contravening the C 90 Standard (I haven't checked a later standard). There
304        was an instance in pcretest which caused it to go wrong when processing
305        \x{...} escapes in subject strings. The has been rewritten to avoid using
306        things like p++ in the argument of isxdigit().
309    Version 8.13 16-Aug-2011
310  ------------------------  ------------------------
312  1.  The Unicode data tables have been updated to Unicode 6.0.0.  1.  The Unicode data tables have been updated to Unicode 6.0.0.
# Line 21  Version 8.13 30-Apr-2011 Line 326  Version 8.13 30-Apr-2011
326      2-byte code at the end of the subject (it thought there wasn't enough data      2-byte code at the end of the subject (it thought there wasn't enough data
327      left).      left).
329    5.  Comprehensive information about what went wrong is now returned by
330        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
331        as the output vector has at least 2 elements. The offset of the start of
332        the failing character and a reason code are placed in the vector.
334    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
335        now returned is for the first byte of the failing character, instead of the
336        last byte inspected. This is an incompatible change, but I hope it is small
337        enough not to be a problem. It makes the returned offset consistent with
338        pcre_exec() and pcre_dfa_exec().
340    7.  pcretest now gives a text phrase as well as the error number when
341        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
342        failure, the offset and reason code are output.
344    8.  When \R was used with a maximizing quantifier it failed to skip backwards
345        over a \r\n pair if the subsequent match failed. Instead, it just skipped
346        back over a single character (\n). This seems wrong (because it treated the
347        two characters as a single entity when going forwards), conflicts with the
348        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
349        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
350        has been changed.
352    9.  Some internal refactoring has changed the processing so that the handling
353        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
354        time (the PCRE_DOTALL option was changed this way some time ago: version
355        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
356        which was always a bit of a fudge. It also means that there is one less
357        argument for the match() function, which reduces its stack requirements
358        slightly. This change also fixes an incompatibility with Perl: the pattern
359        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
361    10. More internal refactoring has drastically reduced the number of recursive
362        calls to match() for possessively repeated groups such as (abc)++ when
363        using pcre_exec().
365    11. While implementing 10, a number of bugs in the handling of groups were
366        discovered and fixed:
368        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
369        (a|)*(?1) gave a compile-time internal error.
370        ((a|)+)+  did not notice that the outer group could match an empty string.
371        (^a|^)+   was not marked as anchored.
372        (.*a|.*)+ was not marked as matching at start or after a newline.
374    12. Yet more internal refactoring has removed another argument from the match()
375        function. Special calls to this function are now indicated by setting a
376        value in a variable in the "match data" data block.
378    13. Be more explicit in pcre_study() instead of relying on "default" for
379        opcodes that mean there is no starting character; this means that when new
380        ones are added and accidentally left out of pcre_study(), testing should
381        pick them up.
383    14. The -s option of pcretest has been documented for ages as being an old
384        synonym of -m (show memory usage). I have changed it to mean "force study
385        for every regex", that is, assume /S for every regex. This is similar to -i
386        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
387        using it. It makes it easier to run collections of tests with and without
388        study enabled, and thereby test pcre_study() more easily. All the standard
389        tests are now run with and without -s (but some patterns can be marked as
390        "never study" - see 20 below).
392    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
393        restoration of the capturing data to the outer values was not happening
394        correctly.
396    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
397        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
398        pattern had matched an empty string, and so incorrectly returned a no
399        match.
401    17. There was optimizing code for the last branch of non-capturing parentheses,
402        and also for the obeyed branch of a conditional subexpression, which used
403        tail recursion to cut down on stack usage. Unfortunately, now that there is
404        the possibility of (*THEN) occurring in these branches, tail recursion is
405        no longer possible because the return has to be checked for (*THEN). These
406        two optimizations have therefore been removed. [But see 8.20/11 above.]
408    18. If a pattern containing \R was studied, it was assumed that \R always
409        matched two bytes, thus causing the minimum subject length to be
410        incorrectly computed because \R can also match just one byte.
412    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
413        was incorrectly computed.
415    20. If /S is present twice on a test pattern in pcretest input, it now
416        *disables* studying, thereby overriding the use of -s on the command line
417        (see 14 above). This is necessary for one or two tests to keep the output
418        identical in both cases.
420    21. When (*ACCEPT) was used in an assertion that matched an empty string and
421        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
423    22. When an atomic group that contained a capturing parenthesis was
424        successfully matched, but the branch in which it appeared failed, the
425        capturing was not being forgotten if a higher numbered group was later
426        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
427        group 1 to "a", when in fact it should be unset. This applied to multi-
428        branched capturing and non-capturing groups, repeated or not, and also to
429        positive assertions (capturing in negative assertions does not happen
430        in PCRE) and also to nested atomic groups.
432    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
433        subject after a captured substring, to make it easier to tell which of a
434        number of identical substrings has been captured.
436    24. The way atomic groups are processed by pcre_exec() has been changed so that
437        if they are repeated, backtracking one repetition now resets captured
438        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
439        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
440        "aaa". Previously, it would have been "a". As part of this code
441        refactoring, the way recursive calls are handled has also been changed.
443    25. If an assertion condition captured any substrings, they were not passed
444        back unless some other capturing happened later. For example, if
445        (?(?=(a))a) was matched against "a", no capturing was returned.
447    26. When studying a pattern that contained subroutine calls or assertions,
448        the code for finding the minimum length of a possible match was handling
449        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
450        group 1 called group 2 while simultaneously a separate group 2 called group
451        1). A stack overflow occurred in this case. I have fixed this by limiting
452        the recursion depth to 10.
454    27. Updated RunTest.bat in the distribution to the version supplied by Tom
455        Fortmann. This supports explicit test numbers on the command line, and has
456        argument validation and error reporting.
458    28. An instance of \X with an unlimited repeat could fail if at any point the
459        first character it looked at was a mark character.
461    29. Some minor code refactoring concerning Unicode properties and scripts
462        should reduce the stack requirement of match() slightly.
464    30. Added the '=' option to pcretest to check the setting of unused capturing
465        slots at the end of the pattern, which are documented as being -1, but are
466        not included in the return count.
468    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
469        compiled something random. Now it gives a compile-time error (as does
470        Perl).
472    32. A *MARK encountered during the processing of a positive assertion is now
473        recorded and passed back (compatible with Perl).
475    33. If --only-matching or --colour was set on a pcregrep call whose pattern
476        had alternative anchored branches, the search for a second match in a line
477        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
478        matched the line "0102" twice. The same bug affected patterns that started
479        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
480        twice.
482    34. Previously, PCRE did not allow quantification of assertions. However, Perl
483        does, and because of capturing effects, quantifying parenthesized
484        assertions may at times be useful. Quantifiers are now allowed for
485        parenthesized assertions.
487    35. A minor code tidy in pcre_compile() when checking options for \R usage.
489    36. \g was being checked for fancy things in a character class, when it should
490        just be a literal "g".
492    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
493        appearance of a nested POSIX class supersedes an apparent external class.
494        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
495        unescaped square brackets may also appear as part of class names. For
496        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
497        more like Perl. (But see 8.20/1 above.)
499    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
500        was because it thought it was \N{name}, which is not supported).
502    39. Add minix to OS list not supporting the -S option in pcretest.
504    40. PCRE tries to detect cases of infinite recursion at compile time, but it
505        cannot analyze patterns in sufficient detail to catch mutual recursions
506        such as ((?1))((?2)). There is now a runtime test that gives an error if a
507        subgroup is called recursively as a subpattern for a second time at the
508        same position in the subject string. In previous releases this might have
509        been caught by the recursion limit, or it might have run out of stack.
511    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
512        happen only once. PCRE was, however incorrectly giving a compile time error
513        "recursive call could loop indefinitely" because it cannot analyze the
514        pattern in sufficient detail. The compile time test no longer happens when
515        PCRE is compiling a conditional subpattern, but actual runaway loops are
516        now caught at runtime (see 40 above).
518    42. It seems that Perl allows any characters other than a closing parenthesis
519        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
520        has been changed to be the same.
522    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
523        as not to get warnings when autogen.sh is called. Also changed
524        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
526    44. To help people who use pcregrep to scan files containing exceedingly long
527        lines, the following changes have been made:
529        (a) The default value of the buffer size parameter has been increased from
530            8K to 20K. (The actual buffer used is three times this size.)
532        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
533            PCRE is built.
535        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
536            to be set at run time.
538        (d) Numerical values in pcregrep options can be followed by K or M, for
539            example --buffer-size=50K.
541        (e) If a line being scanned overflows pcregrep's buffer, an error is now
542            given and the return code is set to 2.
544    45. Add a pointer to the latest mark to the callout data block.
546    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
547        partial match of an empty string instead of no match. This was specific to
548        the use of ".".
550    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
551        complete match instead of a partial match. This bug was dependent on both
552        the PCRE_UTF8 and PCRE_DOTALL options being set.
554    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
555        starting byte set, because \b was not being ignored.
558  Version 8.12 15-Jan-2011  Version 8.12 15-Jan-2011
559  ------------------------  ------------------------

Removed from v.595  
changed lines
  Added in v.914

  ViewVC Help
Powered by ViewVC 1.1.5