ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 553 by ph10, Fri Oct 22 15:57:50 2010 UTC revision 913 by ph10, Sun Feb 12 17:06:59 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.11 10-Oct-2010  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)".
16    Version 8.30 04-February-2012
17    -----------------------------
19    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
20        name is defined in ctype.h.
22    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
23        only in quite long subpatterns.
25    3.  Removed the function pcre_info(), which has been obsolete and deprecated
26        since it was replaced by pcre_fullinfo() in February 2000.
28    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
29        match a (*MARK), and the match failed at the start of the subject, a
30        reference to memory before the start of the subject could occur. This bug
31        was introduced by fix 17 of release 8.21.
33    5.  A reference to an unset group with zero minimum repetition was giving
34        totally wrong answers (in non-JavaScript-compatibility mode). For example,
35        /(another)?(\1?)test/ matched against "hello world test". This bug was
36        introduced in release 8.13.
38    6.  Add support for 16-bit character strings (a large amount of work involving
39        many changes and refactorings).
41    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
42        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
43        from a file.
45    8.  Ovector size of 2 is also supported by JIT based pcre_exec (the ovector size
46        rounding is not applied in this particular case).
48    9.  The invalid Unicode surrogate codepoints U+D800 to U+DFFF are now rejected
49        if they appear, or are escaped, in patterns.
51    10. Get rid of a number of -Wunused-but-set-variable warnings.
53    11. The pattern /(?=(*:x))(q|)/ matches an empty string, and returns the mark
54        "x". The similar pattern /(?=(*:x))((*:y)q|)/ did not return a mark at all.
55        Oddly, Perl behaves the same way. PCRE has been fixed so that this pattern
56        also returns the mark "x". This bug applied to capturing parentheses,
57        non-capturing parentheses, and atomic parentheses. It also applied to some
58        assertions.
60    12. Stephen Kelly's patch to CMakeLists.txt allows it to parse the version
61        information out of configure.ac instead of relying on pcre.h.generic, which
62        is not stored in the repository.
64    13. Applied Dmitry V. Levin's patch for a more portable method for linking with
65        -lreadline.
67    14. ZH added PCRE_CONFIG_JITTARGET; added its output to pcretest -C.
69    15. Applied Graycode's patch to put the top-level frame on the stack rather
70        than the heap when not using the stack for recursion. This gives a
71        performance improvement in many cases when recursion is not deep.
73    16. Experimental code added to "pcretest -C" to output the stack frame size.
76    Version 8.21 12-Dec-2011
77    ------------------------
79    1.  Updating the JIT compiler.
81    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
82        are added as well.
84    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
85        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
86        calling _pcre_jit_exec. Some extra comments are added.
88    4.  (*MARK) settings inside atomic groups that do not contain any capturing
89        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
90        was introduced by change 18 for 8.20.
92    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
93        ECMA-262 standard.
95    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
96        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
97        This bug was probably introduced by change 9 of 8.13.
99    7.  While fixing 6 above, I noticed that a number of other items were being
100        incorrectly rejected as "not fixed length". This arose partly because newer
101        opcodes had not been added to the fixed-length checking code. I have (a)
102        corrected the bug and added tests for these items, and (b) arranged for an
103        error to occur if an unknown opcode is encountered while checking for fixed
104        length instead of just assuming "not fixed length". The items that were
105        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
106        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
107        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
109    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
110        being incorrectly compiled and would have given unpredicatble results.
112    9.  A possessively repeated subpattern with minimum repeat count greater than
113        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
114        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
115        the first (A) could occur when it should not.
117    10. Add a cast and remove a redundant test from the code.
119    11. JIT should use pcre_malloc/pcre_free for allocation.
121    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
122        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
123        is anything other than /usr, -L is still shown).
125    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
127    14. Perl does not support \N without a following name in a [] class; PCRE now
128        also gives an error.
130    15. If a forward reference was repeated with an upper limit of around 2000,
131        it caused the error "internal error: overran compiling workspace". The
132        maximum number of forward references (including repeats) was limited by the
133        internal workspace, and dependent on the LINK_SIZE. The code has been
134        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
135        the default depends on LINK_SIZE. There is a new upper limit (for safety)
136        of around 200,000 forward references. While doing this, I also speeded up
137        the filling in of repeated forward references.
139    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
140        incorrectly expecting the subject to contain another "a" after the start.
142    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
143        in the match, the SKIP should be ignored. This was not happening; instead
144        the SKIP was being treated as NOMATCH. For patterns such as
145        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
146        tested.
148    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
149        now much more compatible with Perl, in particular in cases where the result
150        is a non-match for a non-anchored pattern. For example, if
151        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
152        "m", where previously it did not return a name. A side effect of this
153        change is that for partial matches, the last encountered mark name is
154        returned, as for non matches. A number of tests that were previously not
155        Perl-compatible have been moved into the Perl-compatible test files. The
156        refactoring has had the pleasing side effect of removing one argument from
157        the match() function, thus reducing its stack requirements.
159    19. If the /S+ option was used in pcretest to study a pattern using JIT,
160        subsequent uses of /S (without +) incorrectly behaved like /S+.
162    21. Retrieve executable code size support for the JIT compiler and fixing
163        some warnings.
165    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
166        not work when the shorter character appeared right at the end of the
167        subject string.
169    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
170        systems.
172    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
173        output it when the /M option is used in pcretest.
175    25. The CheckMan script was not being included in the distribution. Also, added
176        an explicit "perl" to run Perl scripts from the PrepareRelease script
177        because this is reportedly needed in Windows.
179    26. If study data was being save in a file and studying had not found a set of
180        "starts with" bytes for the pattern, the data written to the file (though
181        never used) was taken from uninitialized memory and so caused valgrind to
182        complain.
184    27. Updated RunTest.bat as provided by Sheri Pierce.
186    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
188    29. Computation of memory usage for the table of capturing group names was
189        giving an unnecessarily large value.
192    Version 8.20 21-Oct-2011
193    ------------------------
195    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
196        a POSIX class. After further experiments with Perl, which convinced me that
197        Perl has bugs and confusions, a closing square bracket is no longer allowed
198        in a POSIX name. This bug also affected patterns with classes that started
199        with full stops.
201    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
202        captured substring, but while checking the failing first alternative,
203        substring 1 is temporarily captured. If the output vector supplied to
204        pcre_exec() was not big enough for this capture, the yield of the function
205        was still zero ("insufficient space for captured substrings"). This cannot
206        be totally fixed without adding another stack variable, which seems a lot
207        of expense for a edge case. However, I have improved the situation in cases
208        such as /(a)(b)x|abc/ matched against "abc", where the return code
209        indicates that fewer than the maximum number of slots in the ovector have
210        been set.
212    3.  Related to (2) above: when there are more back references in a pattern than
213        slots in the output vector, pcre_exec() uses temporary memory during
214        matching, and copies in the captures as far as possible afterwards. It was
215        using the entire output vector, but this conflicts with the specification
216        that only 2/3 is used for passing back captured substrings. Now it uses
217        only the first 2/3, for compatibility. This is, of course, another edge
218        case.
220    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
221        main code base, and can be used by building with --enable-jit. When this is
222        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
223        runtime --no-jit option is given.
225    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
226        ovector, the return from the function was zero, implying that there were
227        other matches that did not fit. The correct "exactly full" value is now
228        returned.
230    6.  If a subpattern that was called recursively or as a subroutine contained
231        (*PRUNE) or any other control that caused it to give a non-standard return,
232        invalid errors such as "Error -26 (nested recursion at the same subject
233        position)" or even infinite loops could occur.
235    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
236        computing the minimum length on reaching *ACCEPT, and so ended up with the
237        wrong value of 1 rather than 0. Further investigation indicates that
238        computing a minimum subject length in the presence of *ACCEPT is difficult
239        (think back references, subroutine calls), and so I have changed the code
240        so that no minimum is registered for a pattern that contains *ACCEPT.
242    8.  If (*THEN) was present in the first (true) branch of a conditional group,
243        it was not handled as intended. [But see 16 below.]
245    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
246        Sheri Pierce.
248    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
249        the first byte in a match must be "a".
251    11. Change 17 for 8.13 increased the recursion depth for patterns like
252        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
253        pattern contains any instances of (*THEN). If it does not, the old
254        optimizations are restored. It would be nice to do this on a per-group
255        basis, but at the moment that is not feasible.
257    12. In some environments, the output of pcretest -C is CRLF terminated. This
258        broke RunTest's code that checks for the link size. A single white space
259        character after the value is now allowed for.
261    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
262        For "fr", it uses the Windows-specific input and output files.
264    14. If (*THEN) appeared in a group that was called recursively or as a
265        subroutine, it did not work as intended. [But see next item.]
267    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
268        pattern fragments (but not containing any | characters). If A and B are
269        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
270        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
271        D. In other words, Perl considers parentheses that do not contain any |
272        characters to be part of a surrounding alternative, whereas PCRE was
273        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
274        differently. PCRE now behaves in the same way as Perl, except in the case
275        of subroutine/recursion calls such as (?1) which have in any case always
276        been different (but PCRE had them first :-).
278    16. Related to 15 above: Perl does not treat the | in a conditional group as
279        creating alternatives. Such a group is treated in the same way as an
280        ordinary group without any | characters when processing (*THEN). PCRE has
281        been changed to match Perl's behaviour.
283    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
284        RunGrepTest script failed.
286    18. Change 22 for version 13 caused atomic groups to use more stack. This is
287        inevitable for groups that contain captures, but it can lead to a lot of
288        stack use in large patterns. The old behaviour has been restored for atomic
289        groups that do not contain any capturing parentheses.
291    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
292        suppress the check for a minimum subject length at run time. (If it was
293        given to pcre_exec() or pcre_dfa_exec() it did work.)
295    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
296        fail to work when decoding hex characters in data strings in EBCDIC
297        environments.
299    21. It appears that in at least one Mac OS environment, the isxdigit() function
300        is implemented as a macro that evaluates to its argument more than once,
301        contravening the C 90 Standard (I haven't checked a later standard). There
302        was an instance in pcretest which caused it to go wrong when processing
303        \x{...} escapes in subject strings. The has been rewritten to avoid using
304        things like p++ in the argument of isxdigit().
307    Version 8.13 16-Aug-2011
308    ------------------------
310    1.  The Unicode data tables have been updated to Unicode 6.0.0.
312    2.  Two minor typos in pcre_internal.h have been fixed.
314    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
315        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
316        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
318    4.  There were a number of related bugs in the code for matching backrefences
319        caselessly in UTF-8 mode when codes for the characters concerned were
320        different numbers of bytes. For example, U+023A and U+2C65 are an upper
321        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
322        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
323        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
324        2-byte code at the end of the subject (it thought there wasn't enough data
325        left).
327    5.  Comprehensive information about what went wrong is now returned by
328        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
329        as the output vector has at least 2 elements. The offset of the start of
330        the failing character and a reason code are placed in the vector.
332    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
333        now returned is for the first byte of the failing character, instead of the
334        last byte inspected. This is an incompatible change, but I hope it is small
335        enough not to be a problem. It makes the returned offset consistent with
336        pcre_exec() and pcre_dfa_exec().
338    7.  pcretest now gives a text phrase as well as the error number when
339        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
340        failure, the offset and reason code are output.
342    8.  When \R was used with a maximizing quantifier it failed to skip backwards
343        over a \r\n pair if the subsequent match failed. Instead, it just skipped
344        back over a single character (\n). This seems wrong (because it treated the
345        two characters as a single entity when going forwards), conflicts with the
346        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
347        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
348        has been changed.
350    9.  Some internal refactoring has changed the processing so that the handling
351        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
352        time (the PCRE_DOTALL option was changed this way some time ago: version
353        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
354        which was always a bit of a fudge. It also means that there is one less
355        argument for the match() function, which reduces its stack requirements
356        slightly. This change also fixes an incompatibility with Perl: the pattern
357        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
359    10. More internal refactoring has drastically reduced the number of recursive
360        calls to match() for possessively repeated groups such as (abc)++ when
361        using pcre_exec().
363    11. While implementing 10, a number of bugs in the handling of groups were
364        discovered and fixed:
366        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
367        (a|)*(?1) gave a compile-time internal error.
368        ((a|)+)+  did not notice that the outer group could match an empty string.
369        (^a|^)+   was not marked as anchored.
370        (.*a|.*)+ was not marked as matching at start or after a newline.
372    12. Yet more internal refactoring has removed another argument from the match()
373        function. Special calls to this function are now indicated by setting a
374        value in a variable in the "match data" data block.
376    13. Be more explicit in pcre_study() instead of relying on "default" for
377        opcodes that mean there is no starting character; this means that when new
378        ones are added and accidentally left out of pcre_study(), testing should
379        pick them up.
381    14. The -s option of pcretest has been documented for ages as being an old
382        synonym of -m (show memory usage). I have changed it to mean "force study
383        for every regex", that is, assume /S for every regex. This is similar to -i
384        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
385        using it. It makes it easier to run collections of tests with and without
386        study enabled, and thereby test pcre_study() more easily. All the standard
387        tests are now run with and without -s (but some patterns can be marked as
388        "never study" - see 20 below).
390    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
391        restoration of the capturing data to the outer values was not happening
392        correctly.
394    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
395        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
396        pattern had matched an empty string, and so incorrectly returned a no
397        match.
399    17. There was optimizing code for the last branch of non-capturing parentheses,
400        and also for the obeyed branch of a conditional subexpression, which used
401        tail recursion to cut down on stack usage. Unfortunately, now that there is
402        the possibility of (*THEN) occurring in these branches, tail recursion is
403        no longer possible because the return has to be checked for (*THEN). These
404        two optimizations have therefore been removed. [But see 8.20/11 above.]
406    18. If a pattern containing \R was studied, it was assumed that \R always
407        matched two bytes, thus causing the minimum subject length to be
408        incorrectly computed because \R can also match just one byte.
410    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
411        was incorrectly computed.
413    20. If /S is present twice on a test pattern in pcretest input, it now
414        *disables* studying, thereby overriding the use of -s on the command line
415        (see 14 above). This is necessary for one or two tests to keep the output
416        identical in both cases.
418    21. When (*ACCEPT) was used in an assertion that matched an empty string and
419        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
421    22. When an atomic group that contained a capturing parenthesis was
422        successfully matched, but the branch in which it appeared failed, the
423        capturing was not being forgotten if a higher numbered group was later
424        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
425        group 1 to "a", when in fact it should be unset. This applied to multi-
426        branched capturing and non-capturing groups, repeated or not, and also to
427        positive assertions (capturing in negative assertions does not happen
428        in PCRE) and also to nested atomic groups.
430    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
431        subject after a captured substring, to make it easier to tell which of a
432        number of identical substrings has been captured.
434    24. The way atomic groups are processed by pcre_exec() has been changed so that
435        if they are repeated, backtracking one repetition now resets captured
436        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
437        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
438        "aaa". Previously, it would have been "a". As part of this code
439        refactoring, the way recursive calls are handled has also been changed.
441    25. If an assertion condition captured any substrings, they were not passed
442        back unless some other capturing happened later. For example, if
443        (?(?=(a))a) was matched against "a", no capturing was returned.
445    26. When studying a pattern that contained subroutine calls or assertions,
446        the code for finding the minimum length of a possible match was handling
447        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
448        group 1 called group 2 while simultaneously a separate group 2 called group
449        1). A stack overflow occurred in this case. I have fixed this by limiting
450        the recursion depth to 10.
452    27. Updated RunTest.bat in the distribution to the version supplied by Tom
453        Fortmann. This supports explicit test numbers on the command line, and has
454        argument validation and error reporting.
456    28. An instance of \X with an unlimited repeat could fail if at any point the
457        first character it looked at was a mark character.
459    29. Some minor code refactoring concerning Unicode properties and scripts
460        should reduce the stack requirement of match() slightly.
462    30. Added the '=' option to pcretest to check the setting of unused capturing
463        slots at the end of the pattern, which are documented as being -1, but are
464        not included in the return count.
466    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
467        compiled something random. Now it gives a compile-time error (as does
468        Perl).
470    32. A *MARK encountered during the processing of a positive assertion is now
471        recorded and passed back (compatible with Perl).
473    33. If --only-matching or --colour was set on a pcregrep call whose pattern
474        had alternative anchored branches, the search for a second match in a line
475        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
476        matched the line "0102" twice. The same bug affected patterns that started
477        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
478        twice.
480    34. Previously, PCRE did not allow quantification of assertions. However, Perl
481        does, and because of capturing effects, quantifying parenthesized
482        assertions may at times be useful. Quantifiers are now allowed for
483        parenthesized assertions.
485    35. A minor code tidy in pcre_compile() when checking options for \R usage.
487    36. \g was being checked for fancy things in a character class, when it should
488        just be a literal "g".
490    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
491        appearance of a nested POSIX class supersedes an apparent external class.
492        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
493        unescaped square brackets may also appear as part of class names. For
494        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
495        more like Perl. (But see 8.20/1 above.)
497    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
498        was because it thought it was \N{name}, which is not supported).
500    39. Add minix to OS list not supporting the -S option in pcretest.
502    40. PCRE tries to detect cases of infinite recursion at compile time, but it
503        cannot analyze patterns in sufficient detail to catch mutual recursions
504        such as ((?1))((?2)). There is now a runtime test that gives an error if a
505        subgroup is called recursively as a subpattern for a second time at the
506        same position in the subject string. In previous releases this might have
507        been caught by the recursion limit, or it might have run out of stack.
509    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
510        happen only once. PCRE was, however incorrectly giving a compile time error
511        "recursive call could loop indefinitely" because it cannot analyze the
512        pattern in sufficient detail. The compile time test no longer happens when
513        PCRE is compiling a conditional subpattern, but actual runaway loops are
514        now caught at runtime (see 40 above).
516    42. It seems that Perl allows any characters other than a closing parenthesis
517        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
518        has been changed to be the same.
520    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
521        as not to get warnings when autogen.sh is called. Also changed
522        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
524    44. To help people who use pcregrep to scan files containing exceedingly long
525        lines, the following changes have been made:
527        (a) The default value of the buffer size parameter has been increased from
528            8K to 20K. (The actual buffer used is three times this size.)
530        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
531            PCRE is built.
533        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
534            to be set at run time.
536        (d) Numerical values in pcregrep options can be followed by K or M, for
537            example --buffer-size=50K.
539        (e) If a line being scanned overflows pcregrep's buffer, an error is now
540            given and the return code is set to 2.
542    45. Add a pointer to the latest mark to the callout data block.
544    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
545        partial match of an empty string instead of no match. This was specific to
546        the use of ".".
548    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
549        complete match instead of a partial match. This bug was dependent on both
550        the PCRE_UTF8 and PCRE_DOTALL options being set.
552    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
553        starting byte set, because \b was not being ignored.
556    Version 8.12 15-Jan-2011
557    ------------------------
559    1.  Fixed some typos in the markup of the man pages, and wrote a script that
560        checks for such things as part of the documentation building process.
562    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
563        --match-limit and --recursion-limit options (added for 8.11). In
564        particular, this made one of the standard tests fail. (The integer value
565        went into the wrong half of a long int.)
567    3.  If the --colour option was given to pcregrep with -v (invert match), it
568        did strange things, either producing crazy output, or crashing. It should,
569        of course, ignore a request for colour when reporting lines that do not
570        match.
572    4.  Another pcregrep bug caused similar problems if --colour was specified with
573        -M (multiline) and the pattern match finished with a line ending.
575    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
576        matched in multiline mode, the following line was shown as part of the
577        match. This seems wrong, so I have changed it.
579    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
580        the check for further matches in the same line (so they could be coloured)
581        to overrun the end of the current line. If another match was found, it was
582        incorrectly shown (and then shown again when found in the next line).
584    7.  If pcregrep was compiled under Windows, there was a reference to the
585        function pcregrep_exit() before it was defined. I am assuming this was
586        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
587        reported by a user. I've moved the definition above the reference.
590    Version 8.11 10-Dec-2010
591  ------------------------  ------------------------
593  1.  (*THEN) was not working properly if there were untried alternatives prior  1.  (*THEN) was not working properly if there were untried alternatives prior
594      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it      to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
595      backtracked to try for "b" instead of moving to the next alternative branch      backtracked to try for "b" instead of moving to the next alternative branch
596      at the same level (in this case, to look for "c"). The Perl documentation      at the same level (in this case, to look for "c"). The Perl documentation
597      is clear that when (*THEN) is backtracked onto, it goes to the "next      is clear that when (*THEN) is backtracked onto, it goes to the "next
598      alternative in the innermost enclosing group".      alternative in the innermost enclosing group".
600  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern  2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
601      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should      such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
602      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and      result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
603      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides      (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
604      (*THEN).      (*THEN).
606  3.  If \s appeared in a character class, it removed the VT character from  3.  If \s appeared in a character class, it removed the VT character from
607      the class, even if it had been included by some previous item, for example      the class, even if it had been included by some previous item, for example
608      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part      in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
609      of \s, but is part of the POSIX "space" class.)      of \s, but is part of the POSIX "space" class.)
611  4.  A partial match never returns an empty string (because you can always  4.  A partial match never returns an empty string (because you can always
612      match an empty string at the end of the subject); however the checking for      match an empty string at the end of the subject); however the checking for
613      an empty string was starting at the "start of match" point. This has been      an empty string was starting at the "start of match" point. This has been
# Line 31  Version 8.11 10-Oct-2010 Line 617  Version 8.11 10-Oct-2010
617      (previously it gave "no match").      (previously it gave "no match").
619  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching  5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
620      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,      of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
621      previously a full match would be given. However, setting PCRE_PARTIAL_HARD      previously a full match would be given. However, setting PCRE_PARTIAL_HARD
622      has an implication that the given string is incomplete (because a partial      has an implication that the given string is incomplete (because a partial
623      match is preferred over a full match). For this reason, these items now      match is preferred over a full match). For this reason, these items now
624      give a partial match in this situation. [Aside: previously, the one case      give a partial match in this situation. [Aside: previously, the one case
625      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial      /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
626      match rather than a full match, which was wrong by the old rules, but is      match rather than a full match, which was wrong by the old rules, but is
627      now correct.]      now correct.]
629    6.  There was a bug in the handling of #-introduced comments, recognized when
630        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
631        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
632        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
633        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
634        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
635        places in pcre_compile().
637    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
638        comments when looking ahead for named forward references to subpatterns,
639        the only newline sequence it recognized was NL. It now handles newlines
640        according to the set newline convention.
642    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
643        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
644        cater for a lack of strerror(). These oversights have been fixed.
646    9.  Added --match-limit and --recursion-limit to pcregrep.
648    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
650    11. When the -o option was used, pcregrep was setting a return code of 1, even
651        when matches were found, and --line-buffered was not being honoured.
653    12. Added an optional parentheses number to the -o and --only-matching options
654        of pcregrep.
656    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
657        can match an empty string. The code to do it in pcretest and pcredemo
658        needed fixing:
660        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
661            only one byte after an empty string match just before CRLF (this case
662            just got forgotten; "any" and "anycrlf" were OK).
664        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
665            mode when an empty string match preceded an ASCII character followed by
666            a non-ASCII character. (The code for advancing by one character rather
667            than one byte was nonsense.)
669        (c) The pcredemo.c sample program did not have any code at all to handle
670            the cases when CRLF is a valid newline sequence.
672    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
673        as a starting offset was within the subject string. There is now a new
674        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
675        negative or greater than the length of the string. In order to test this,
676        pcretest is extended to allow the setting of negative starting offsets.
678    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
679        starting offset points to the beginning of a UTF-8 character was
680        unnecessarily clumsy. I tidied it up.
682    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
683        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
685    17. Nobody had reported that the --include_dir option, which was added in
686        release 7.7 should have been called --include-dir (hyphen, not underscore)
687        for compatibility with GNU grep. I have changed it to --include-dir, but
688        left --include_dir as an undocumented synonym, and the same for
689        --exclude-dir, though that is not available in GNU grep, at least as of
690        release 2.5.4.
692    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
693        characters from a string of bytes) have been redefined so as not to use
694        loops, in order to improve performance in some environments. At the same
695        time, I abstracted some of the common code into auxiliary macros to save
696        repetition (this should not affect the compiled code).
698    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
699        compile-time error is now given if \c is not followed by an ASCII
700        character, that is, a byte less than 128. (In EBCDIC mode, the code is
701        different, and any byte value is allowed.)
703    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
704        START_OPTIMIZE option, which is now allowed at compile time - but just
705        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
706        to pcregrep and other applications that have no direct access to PCRE
707        options. The new /Y option in pcretest sets this option when calling
708        pcre_compile().
710    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
711        back references. Groups containing recursive back references were forced to
712        be atomic by that change, but in the case of named groups, the amount of
713        memory required was incorrectly computed, leading to "Failed: internal
714        error: code overflow". This has been fixed.
716    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
717        pcretest.c, to avoid build problems in some Borland environments.
720  Version 8.10 25-Jun-2010  Version 8.10 25-Jun-2010

Removed from v.553  
changed lines
  Added in v.913

  ViewVC Help
Powered by ViewVC 1.1.5