ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 517 by ph10, Wed May 5 10:44:20 2010 UTC revision 856 by ph10, Sat Jan 7 17:02:55 2012 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.10 03 May-2010  Version 8.30
5    ------------
7    1.  Renamed "isnumber" as "is_a_number" because in some Mac environments this
8        name is defined in ctype.h.
10    2.  Fixed a bug in fixed-length calculation for lookbehinds that would show up
11        only in quite long subpatterns.
13    3.  Removed the function pcre_info(), which has been obsolete and deprecated
14        since it was replaced by pcre_fullinfo() in February 2000.
16    4.  For a non-anchored pattern, if (*SKIP) was given with a name that did not
17        match a (*MARK), and the match failed at the start of the subject, a
18        reference to memory before the start of the subject could occur. This bug
19        was introduced by fix 17 of release 8.21.
21    5.  A reference to an unset group with zero minimum repetition was giving
22        totally wrong answers (in non-JavaScript-compatibility mode). For example,
23        /(another)?(\1?)test/ matched against "hello world test". This bug was
24        introduced in release 8.13.
26    6.  Add support for 16-bit character strings (a large amount of work involving
27        many changes and refactorings).
29    7.  RunGrepTest failed on msys because \r\n was replaced by whitespace when the
30        command "pattern=`printf 'xxx\r\njkl'`" was run. The pattern is now taken
31        from a file.
34    Version 8.21 12-Dec-2011
35    ------------------------
37    1.  Updating the JIT compiler.
39    2.  JIT compiler now supports OP_NCREF, OP_RREF and OP_NRREF. New test cases
40        are added as well.
42    3.  Fix cache-flush issue on PowerPC (It is still an experimental JIT port).
43        PCRE_EXTRA_TABLES is not suported by JIT, and should be checked before
44        calling _pcre_jit_exec. Some extra comments are added.
46    4.  (*MARK) settings inside atomic groups that do not contain any capturing
47        parentheses, for example, (?>a(*:m)), were not being passed out. This bug
48        was introduced by change 18 for 8.20.
50    5.  Supporting of \x, \U and \u in JavaScript compatibility mode based on the
51        ECMA-262 standard.
53    6.  Lookbehinds such as (?<=a{2}b) that contained a fixed repetition were
54        erroneously being rejected as "not fixed length" if PCRE_CASELESS was set.
55        This bug was probably introduced by change 9 of 8.13.
57    7.  While fixing 6 above, I noticed that a number of other items were being
58        incorrectly rejected as "not fixed length". This arose partly because newer
59        opcodes had not been added to the fixed-length checking code. I have (a)
60        corrected the bug and added tests for these items, and (b) arranged for an
61        error to occur if an unknown opcode is encountered while checking for fixed
62        length instead of just assuming "not fixed length". The items that were
63        rejected were: (*ACCEPT), (*COMMIT), (*FAIL), (*MARK), (*PRUNE), (*SKIP),
64        (*THEN), \h, \H, \v, \V, and single character negative classes with fixed
65        repetitions, e.g. [^a]{3}, with and without PCRE_CASELESS.
67    8.  A possessively repeated conditional subpattern such as (?(?=c)c|d)++ was
68        being incorrectly compiled and would have given unpredicatble results.
70    9.  A possessively repeated subpattern with minimum repeat count greater than
71        one behaved incorrectly. For example, (A){2,}+ behaved as if it was
72        (A)(A)++ which meant that, after a subsequent mismatch, backtracking into
73        the first (A) could occur when it should not.
75    10. Add a cast and remove a redundant test from the code.
77    11. JIT should use pcre_malloc/pcre_free for allocation.
79    12. Updated pcre-config so that it no longer shows -L/usr/lib, which seems
80        best practice nowadays, and helps with cross-compiling. (If the exec_prefix
81        is anything other than /usr, -L is still shown).
83    13. In non-UTF-8 mode, \C is now supported in lookbehinds and DFA matching.
85    14. Perl does not support \N without a following name in a [] class; PCRE now
86        also gives an error.
88    15. If a forward reference was repeated with an upper limit of around 2000,
89        it caused the error "internal error: overran compiling workspace". The
90        maximum number of forward references (including repeats) was limited by the
91        internal workspace, and dependent on the LINK_SIZE. The code has been
92        rewritten so that the workspace expands (via pcre_malloc) if necessary, and
93        the default depends on LINK_SIZE. There is a new upper limit (for safety)
94        of around 200,000 forward references. While doing this, I also speeded up
95        the filling in of repeated forward references.
97    16. A repeated forward reference in a pattern such as (a)(?2){2}(.) was
98        incorrectly expecting the subject to contain another "a" after the start.
100    17. When (*SKIP:name) is activated without a corresponding (*MARK:name) earlier
101        in the match, the SKIP should be ignored. This was not happening; instead
102        the SKIP was being treated as NOMATCH. For patterns such as
103        /A(*MARK:A)A+(*SKIP:B)Z|AAC/ this meant that the AAC branch was never
104        tested.
106    18. The behaviour of (*MARK), (*PRUNE), and (*THEN) has been reworked and is
107        now much more compatible with Perl, in particular in cases where the result
108        is a non-match for a non-anchored pattern. For example, if
109        /b(*:m)f|a(*:n)w/ is matched against "abc", the non-match returns the name
110        "m", where previously it did not return a name. A side effect of this
111        change is that for partial matches, the last encountered mark name is
112        returned, as for non matches. A number of tests that were previously not
113        Perl-compatible have been moved into the Perl-compatible test files. The
114        refactoring has had the pleasing side effect of removing one argument from
115        the match() function, thus reducing its stack requirements.
117    19. If the /S+ option was used in pcretest to study a pattern using JIT,
118        subsequent uses of /S (without +) incorrectly behaved like /S+.
120    21. Retrieve executable code size support for the JIT compiler and fixing
121        some warnings.
123    22. A caseless match of a UTF-8 character whose other case uses fewer bytes did
124        not work when the shorter character appeared right at the end of the
125        subject string.
127    23. Added some (int) casts to non-JIT modules to reduce warnings on 64-bit
128        systems.
130    24. Added PCRE_INFO_JITSIZE to pass on the value from (21) above, and also
131        output it when the /M option is used in pcretest.
133    25. The CheckMan script was not being included in the distribution. Also, added
134        an explicit "perl" to run Perl scripts from the PrepareRelease script
135        because this is reportedly needed in Windows.
137    26. If study data was being save in a file and studying had not found a set of
138        "starts with" bytes for the pattern, the data written to the file (though
139        never used) was taken from uninitialized memory and so caused valgrind to
140        complain.
142    27. Updated RunTest.bat as provided by Sheri Pierce.
144    28. Fixed a possible uninitialized memory bug in pcre_jit_compile.c.
146    29. Computation of memory usage for the table of capturing group names was
147        giving an unnecessarily large value.
150    Version 8.20 21-Oct-2011
151    ------------------------
153    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
154        a POSIX class. After further experiments with Perl, which convinced me that
155        Perl has bugs and confusions, a closing square bracket is no longer allowed
156        in a POSIX name. This bug also affected patterns with classes that started
157        with full stops.
159    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
160        captured substring, but while checking the failing first alternative,
161        substring 1 is temporarily captured. If the output vector supplied to
162        pcre_exec() was not big enough for this capture, the yield of the function
163        was still zero ("insufficient space for captured substrings"). This cannot
164        be totally fixed without adding another stack variable, which seems a lot
165        of expense for a edge case. However, I have improved the situation in cases
166        such as /(a)(b)x|abc/ matched against "abc", where the return code
167        indicates that fewer than the maximum number of slots in the ovector have
168        been set.
170    3.  Related to (2) above: when there are more back references in a pattern than
171        slots in the output vector, pcre_exec() uses temporary memory during
172        matching, and copies in the captures as far as possible afterwards. It was
173        using the entire output vector, but this conflicts with the specification
174        that only 2/3 is used for passing back captured substrings. Now it uses
175        only the first 2/3, for compatibility. This is, of course, another edge
176        case.
178    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
179        main code base, and can be used by building with --enable-jit. When this is
180        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
181        runtime --no-jit option is given.
183    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
184        ovector, the return from the function was zero, implying that there were
185        other matches that did not fit. The correct "exactly full" value is now
186        returned.
188    6.  If a subpattern that was called recursively or as a subroutine contained
189        (*PRUNE) or any other control that caused it to give a non-standard return,
190        invalid errors such as "Error -26 (nested recursion at the same subject
191        position)" or even infinite loops could occur.
193    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
194        computing the minimum length on reaching *ACCEPT, and so ended up with the
195        wrong value of 1 rather than 0. Further investigation indicates that
196        computing a minimum subject length in the presence of *ACCEPT is difficult
197        (think back references, subroutine calls), and so I have changed the code
198        so that no minimum is registered for a pattern that contains *ACCEPT.
200    8.  If (*THEN) was present in the first (true) branch of a conditional group,
201        it was not handled as intended. [But see 16 below.]
203    9.  Replaced RunTest.bat and CMakeLists.txt with improved versions provided by
204        Sheri Pierce.
206    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
207        the first byte in a match must be "a".
209    11. Change 17 for 8.13 increased the recursion depth for patterns like
210        /a(?:.)*?a/ drastically. I've improved things by remembering whether a
211        pattern contains any instances of (*THEN). If it does not, the old
212        optimizations are restored. It would be nice to do this on a per-group
213        basis, but at the moment that is not feasible.
215    12. In some environments, the output of pcretest -C is CRLF terminated. This
216        broke RunTest's code that checks for the link size. A single white space
217        character after the value is now allowed for.
219    13. RunTest now checks for the "fr" locale as well as for "fr_FR" and "french".
220        For "fr", it uses the Windows-specific input and output files.
222    14. If (*THEN) appeared in a group that was called recursively or as a
223        subroutine, it did not work as intended. [But see next item.]
225    15. Consider the pattern /A (B(*THEN)C) | D/ where A, B, C, and D are complex
226        pattern fragments (but not containing any | characters). If A and B are
227        matched, but there is a failure in C so that it backtracks to (*THEN), PCRE
228        was behaving differently to Perl. PCRE backtracked into A, but Perl goes to
229        D. In other words, Perl considers parentheses that do not contain any |
230        characters to be part of a surrounding alternative, whereas PCRE was
231        treading (B(*THEN)C) the same as (B(*THEN)C|(*FAIL)) -- which Perl handles
232        differently. PCRE now behaves in the same way as Perl, except in the case
233        of subroutine/recursion calls such as (?1) which have in any case always
234        been different (but PCRE had them first :-).
236    16. Related to 15 above: Perl does not treat the | in a conditional group as
237        creating alternatives. Such a group is treated in the same way as an
238        ordinary group without any | characters when processing (*THEN). PCRE has
239        been changed to match Perl's behaviour.
241    17. If a user had set PCREGREP_COLO(U)R to something other than 1:31, the
242        RunGrepTest script failed.
244    18. Change 22 for version 13 caused atomic groups to use more stack. This is
245        inevitable for groups that contain captures, but it can lead to a lot of
246        stack use in large patterns. The old behaviour has been restored for atomic
247        groups that do not contain any capturing parentheses.
249    19. If the PCRE_NO_START_OPTIMIZE option was set for pcre_compile(), it did not
250        suppress the check for a minimum subject length at run time. (If it was
251        given to pcre_exec() or pcre_dfa_exec() it did work.)
253    20. Fixed an ASCII-dependent infelicity in pcretest that would have made it
254        fail to work when decoding hex characters in data strings in EBCDIC
255        environments.
257    21. It appears that in at least one Mac OS environment, the isxdigit() function
258        is implemented as a macro that evaluates to its argument more than once,
259        contravening the C 90 Standard (I haven't checked a later standard). There
260        was an instance in pcretest which caused it to go wrong when processing
261        \x{...} escapes in subject strings. The has been rewritten to avoid using
262        things like p++ in the argument of isxdigit().
265    Version 8.13 16-Aug-2011
266    ------------------------
268    1.  The Unicode data tables have been updated to Unicode 6.0.0.
270    2.  Two minor typos in pcre_internal.h have been fixed.
272    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
273        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
274        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
276    4.  There were a number of related bugs in the code for matching backrefences
277        caselessly in UTF-8 mode when codes for the characters concerned were
278        different numbers of bytes. For example, U+023A and U+2C65 are an upper
279        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
280        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
281        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
282        2-byte code at the end of the subject (it thought there wasn't enough data
283        left).
285    5.  Comprehensive information about what went wrong is now returned by
286        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
287        as the output vector has at least 2 elements. The offset of the start of
288        the failing character and a reason code are placed in the vector.
290    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
291        now returned is for the first byte of the failing character, instead of the
292        last byte inspected. This is an incompatible change, but I hope it is small
293        enough not to be a problem. It makes the returned offset consistent with
294        pcre_exec() and pcre_dfa_exec().
296    7.  pcretest now gives a text phrase as well as the error number when
297        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
298        failure, the offset and reason code are output.
300    8.  When \R was used with a maximizing quantifier it failed to skip backwards
301        over a \r\n pair if the subsequent match failed. Instead, it just skipped
302        back over a single character (\n). This seems wrong (because it treated the
303        two characters as a single entity when going forwards), conflicts with the
304        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
305        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
306        has been changed.
308    9.  Some internal refactoring has changed the processing so that the handling
309        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
310        time (the PCRE_DOTALL option was changed this way some time ago: version
311        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
312        which was always a bit of a fudge. It also means that there is one less
313        argument for the match() function, which reduces its stack requirements
314        slightly. This change also fixes an incompatibility with Perl: the pattern
315        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
317    10. More internal refactoring has drastically reduced the number of recursive
318        calls to match() for possessively repeated groups such as (abc)++ when
319        using pcre_exec().
321    11. While implementing 10, a number of bugs in the handling of groups were
322        discovered and fixed:
324        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
325        (a|)*(?1) gave a compile-time internal error.
326        ((a|)+)+  did not notice that the outer group could match an empty string.
327        (^a|^)+   was not marked as anchored.
328        (.*a|.*)+ was not marked as matching at start or after a newline.
330    12. Yet more internal refactoring has removed another argument from the match()
331        function. Special calls to this function are now indicated by setting a
332        value in a variable in the "match data" data block.
334    13. Be more explicit in pcre_study() instead of relying on "default" for
335        opcodes that mean there is no starting character; this means that when new
336        ones are added and accidentally left out of pcre_study(), testing should
337        pick them up.
339    14. The -s option of pcretest has been documented for ages as being an old
340        synonym of -m (show memory usage). I have changed it to mean "force study
341        for every regex", that is, assume /S for every regex. This is similar to -i
342        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
343        using it. It makes it easier to run collections of tests with and without
344        study enabled, and thereby test pcre_study() more easily. All the standard
345        tests are now run with and without -s (but some patterns can be marked as
346        "never study" - see 20 below).
348    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
349        restoration of the capturing data to the outer values was not happening
350        correctly.
352    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
353        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
354        pattern had matched an empty string, and so incorrectly returned a no
355        match.
357    17. There was optimizing code for the last branch of non-capturing parentheses,
358        and also for the obeyed branch of a conditional subexpression, which used
359        tail recursion to cut down on stack usage. Unfortunately, now that there is
360        the possibility of (*THEN) occurring in these branches, tail recursion is
361        no longer possible because the return has to be checked for (*THEN). These
362        two optimizations have therefore been removed. [But see 8.20/11 above.]
364    18. If a pattern containing \R was studied, it was assumed that \R always
365        matched two bytes, thus causing the minimum subject length to be
366        incorrectly computed because \R can also match just one byte.
368    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
369        was incorrectly computed.
371    20. If /S is present twice on a test pattern in pcretest input, it now
372        *disables* studying, thereby overriding the use of -s on the command line
373        (see 14 above). This is necessary for one or two tests to keep the output
374        identical in both cases.
376    21. When (*ACCEPT) was used in an assertion that matched an empty string and
377        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
379    22. When an atomic group that contained a capturing parenthesis was
380        successfully matched, but the branch in which it appeared failed, the
381        capturing was not being forgotten if a higher numbered group was later
382        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
383        group 1 to "a", when in fact it should be unset. This applied to multi-
384        branched capturing and non-capturing groups, repeated or not, and also to
385        positive assertions (capturing in negative assertions does not happen
386        in PCRE) and also to nested atomic groups.
388    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
389        subject after a captured substring, to make it easier to tell which of a
390        number of identical substrings has been captured.
392    24. The way atomic groups are processed by pcre_exec() has been changed so that
393        if they are repeated, backtracking one repetition now resets captured
394        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
395        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
396        "aaa". Previously, it would have been "a". As part of this code
397        refactoring, the way recursive calls are handled has also been changed.
399    25. If an assertion condition captured any substrings, they were not passed
400        back unless some other capturing happened later. For example, if
401        (?(?=(a))a) was matched against "a", no capturing was returned.
403    26. When studying a pattern that contained subroutine calls or assertions,
404        the code for finding the minimum length of a possible match was handling
405        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
406        group 1 called group 2 while simultaneously a separate group 2 called group
407        1). A stack overflow occurred in this case. I have fixed this by limiting
408        the recursion depth to 10.
410    27. Updated RunTest.bat in the distribution to the version supplied by Tom
411        Fortmann. This supports explicit test numbers on the command line, and has
412        argument validation and error reporting.
414    28. An instance of \X with an unlimited repeat could fail if at any point the
415        first character it looked at was a mark character.
417    29. Some minor code refactoring concerning Unicode properties and scripts
418        should reduce the stack requirement of match() slightly.
420    30. Added the '=' option to pcretest to check the setting of unused capturing
421        slots at the end of the pattern, which are documented as being -1, but are
422        not included in the return count.
424    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
425        compiled something random. Now it gives a compile-time error (as does
426        Perl).
428    32. A *MARK encountered during the processing of a positive assertion is now
429        recorded and passed back (compatible with Perl).
431    33. If --only-matching or --colour was set on a pcregrep call whose pattern
432        had alternative anchored branches, the search for a second match in a line
433        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
434        matched the line "0102" twice. The same bug affected patterns that started
435        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
436        twice.
438    34. Previously, PCRE did not allow quantification of assertions. However, Perl
439        does, and because of capturing effects, quantifying parenthesized
440        assertions may at times be useful. Quantifiers are now allowed for
441        parenthesized assertions.
443    35. A minor code tidy in pcre_compile() when checking options for \R usage.
445    36. \g was being checked for fancy things in a character class, when it should
446        just be a literal "g".
448    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
449        appearance of a nested POSIX class supersedes an apparent external class.
450        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
451        unescaped square brackets may also appear as part of class names. For
452        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
453        more like Perl. (But see 8.20/1 above.)
455    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
456        was because it thought it was \N{name}, which is not supported).
458    39. Add minix to OS list not supporting the -S option in pcretest.
460    40. PCRE tries to detect cases of infinite recursion at compile time, but it
461        cannot analyze patterns in sufficient detail to catch mutual recursions
462        such as ((?1))((?2)). There is now a runtime test that gives an error if a
463        subgroup is called recursively as a subpattern for a second time at the
464        same position in the subject string. In previous releases this might have
465        been caught by the recursion limit, or it might have run out of stack.
467    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
468        happen only once. PCRE was, however incorrectly giving a compile time error
469        "recursive call could loop indefinitely" because it cannot analyze the
470        pattern in sufficient detail. The compile time test no longer happens when
471        PCRE is compiling a conditional subpattern, but actual runaway loops are
472        now caught at runtime (see 40 above).
474    42. It seems that Perl allows any characters other than a closing parenthesis
475        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
476        has been changed to be the same.
478    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
479        as not to get warnings when autogen.sh is called. Also changed
480        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
482    44. To help people who use pcregrep to scan files containing exceedingly long
483        lines, the following changes have been made:
485        (a) The default value of the buffer size parameter has been increased from
486            8K to 20K. (The actual buffer used is three times this size.)
488        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
489            PCRE is built.
491        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
492            to be set at run time.
494        (d) Numerical values in pcregrep options can be followed by K or M, for
495            example --buffer-size=50K.
497        (e) If a line being scanned overflows pcregrep's buffer, an error is now
498            given and the return code is set to 2.
500    45. Add a pointer to the latest mark to the callout data block.
502    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
503        partial match of an empty string instead of no match. This was specific to
504        the use of ".".
506    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
507        complete match instead of a partial match. This bug was dependent on both
508        the PCRE_UTF8 and PCRE_DOTALL options being set.
510    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
511        starting byte set, because \b was not being ignored.
514    Version 8.12 15-Jan-2011
515    ------------------------
517    1.  Fixed some typos in the markup of the man pages, and wrote a script that
518        checks for such things as part of the documentation building process.
520    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
521        --match-limit and --recursion-limit options (added for 8.11). In
522        particular, this made one of the standard tests fail. (The integer value
523        went into the wrong half of a long int.)
525    3.  If the --colour option was given to pcregrep with -v (invert match), it
526        did strange things, either producing crazy output, or crashing. It should,
527        of course, ignore a request for colour when reporting lines that do not
528        match.
530    4.  Another pcregrep bug caused similar problems if --colour was specified with
531        -M (multiline) and the pattern match finished with a line ending.
533    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
534        matched in multiline mode, the following line was shown as part of the
535        match. This seems wrong, so I have changed it.
537    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
538        the check for further matches in the same line (so they could be coloured)
539        to overrun the end of the current line. If another match was found, it was
540        incorrectly shown (and then shown again when found in the next line).
542    7.  If pcregrep was compiled under Windows, there was a reference to the
543        function pcregrep_exit() before it was defined. I am assuming this was
544        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
545        reported by a user. I've moved the definition above the reference.
548    Version 8.11 10-Dec-2010
549    ------------------------
551    1.  (*THEN) was not working properly if there were untried alternatives prior
552        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
553        backtracked to try for "b" instead of moving to the next alternative branch
554        at the same level (in this case, to look for "c"). The Perl documentation
555        is clear that when (*THEN) is backtracked onto, it goes to the "next
556        alternative in the innermost enclosing group".
558    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
559        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
560        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
561        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
562        (*THEN).
564    3.  If \s appeared in a character class, it removed the VT character from
565        the class, even if it had been included by some previous item, for example
566        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
567        of \s, but is part of the POSIX "space" class.)
569    4.  A partial match never returns an empty string (because you can always
570        match an empty string at the end of the subject); however the checking for
571        an empty string was starting at the "start of match" point. This has been
572        changed to the "earliest inspected character" point, because the returned
573        data for a partial match starts at this character. This means that, for
574        example, /(?<=abc)def/ gives a partial match for the subject "abc"
575        (previously it gave "no match").
577    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
578        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
579        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
580        has an implication that the given string is incomplete (because a partial
581        match is preferred over a full match). For this reason, these items now
582        give a partial match in this situation. [Aside: previously, the one case
583        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
584        match rather than a full match, which was wrong by the old rules, but is
585        now correct.]
587    6.  There was a bug in the handling of #-introduced comments, recognized when
588        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
589        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
590        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
591        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
592        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
593        places in pcre_compile().
595    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
596        comments when looking ahead for named forward references to subpatterns,
597        the only newline sequence it recognized was NL. It now handles newlines
598        according to the set newline convention.
600    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
601        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
602        cater for a lack of strerror(). These oversights have been fixed.
604    9.  Added --match-limit and --recursion-limit to pcregrep.
606    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
608    11. When the -o option was used, pcregrep was setting a return code of 1, even
609        when matches were found, and --line-buffered was not being honoured.
611    12. Added an optional parentheses number to the -o and --only-matching options
612        of pcregrep.
614    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
615        can match an empty string. The code to do it in pcretest and pcredemo
616        needed fixing:
618        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
619            only one byte after an empty string match just before CRLF (this case
620            just got forgotten; "any" and "anycrlf" were OK).
622        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
623            mode when an empty string match preceded an ASCII character followed by
624            a non-ASCII character. (The code for advancing by one character rather
625            than one byte was nonsense.)
627        (c) The pcredemo.c sample program did not have any code at all to handle
628            the cases when CRLF is a valid newline sequence.
630    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
631        as a starting offset was within the subject string. There is now a new
632        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
633        negative or greater than the length of the string. In order to test this,
634        pcretest is extended to allow the setting of negative starting offsets.
636    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
637        starting offset points to the beginning of a UTF-8 character was
638        unnecessarily clumsy. I tidied it up.
640    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
641        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
643    17. Nobody had reported that the --include_dir option, which was added in
644        release 7.7 should have been called --include-dir (hyphen, not underscore)
645        for compatibility with GNU grep. I have changed it to --include-dir, but
646        left --include_dir as an undocumented synonym, and the same for
647        --exclude-dir, though that is not available in GNU grep, at least as of
648        release 2.5.4.
650    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
651        characters from a string of bytes) have been redefined so as not to use
652        loops, in order to improve performance in some environments. At the same
653        time, I abstracted some of the common code into auxiliary macros to save
654        repetition (this should not affect the compiled code).
656    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
657        compile-time error is now given if \c is not followed by an ASCII
658        character, that is, a byte less than 128. (In EBCDIC mode, the code is
659        different, and any byte value is allowed.)
661    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
662        START_OPTIMIZE option, which is now allowed at compile time - but just
663        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
664        to pcregrep and other applications that have no direct access to PCRE
665        options. The new /Y option in pcretest sets this option when calling
666        pcre_compile().
668    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
669        back references. Groups containing recursive back references were forced to
670        be atomic by that change, but in the case of named groups, the amount of
671        memory required was incorrectly computed, leading to "Failed: internal
672        error: code overflow". This has been fixed.
674    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
675        pcretest.c, to avoid build problems in some Borland environments.
678    Version 8.10 25-Jun-2010
679  ------------------------  ------------------------
681  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
# Line 9  Version 8.10 03 May-2010 Line 683  Version 8.10 03 May-2010
684  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
686  3.  Inside a character class, \B is treated as a literal by default, but  3.  Inside a character class, \B is treated as a literal by default, but
687      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
688      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
690  4.  Inside a character class, PCRE always treated \R and \X as literals,  4.  Inside a character class, PCRE always treated \R and \X as literals,
691      whereas Perl faults them if its -w option is set. I have changed PCRE so      whereas Perl faults them if its -w option is set. I have changed PCRE so
692      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
694  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
695      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
697  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
698      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
699      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
700      result to (void) does not stop the warnings; a more elaborate fudge is      result to (void) does not stop the warnings; a more elaborate fudge is
701      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
703  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
705  8.  Added four artifical Unicode properties to help with an option to make  8.  Added four artifical Unicode properties to help with an option to make
706      \s etc use properties. The new properties are: Xan (alphanumeric), Xsp      \s etc use properties (see next item). The new properties are: Xan
707      (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
709    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
710        use Unicode properties. (*UCP) at the start of a pattern can be used to set
711        this option. Modified pcretest to add /W to test this facility. Added
712        REG_UCP to make it available via the POSIX interface.
714    10. Added --line-buffered to pcregrep.
716    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
717        studied, and the match started with a letter with a code point greater than
718        127 whose first byte was different to the first byte of the other case of
719        the letter, the other case of this starting letter was not recognized
720        (#976).
722    12. If a pattern that was studied started with a repeated Unicode property
723        test, for example, \p{Nd}+, there was the theoretical possibility of
724        setting up an incorrect bitmap of starting bytes, but fortunately it could
725        not have actually happened in practice until change 8 above was made (it
726        added property types that matched character-matching opcodes).
728    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
729        possible starting bytes for non-anchored patterns.
731    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
732        \R, and also a number of cases that involve Unicode properties, both
733        explicit and implicit when PCRE_UCP is set.
735    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
736        input, it could crash or give wrong results if characters with values
737        greater than 0xc0 were present in the subject string. (Detail: it assumed
738        UTF-8 input when processing these items.)
740    16. Added a lot of (int) casts to avoid compiler warnings in systems where
741        size_t is 64-bit (#991).
743    17. Added a check for running out of memory when PCRE is compiled with
744        --disable-stack-for-recursion (#990).
746    18. If the last data line in a file for pcretest does not have a newline on
747        the end, a newline was missing in the output.
749    19. The default pcre_chartables.c file recognizes only ASCII characters (values
750        less than 128) in its various bitmaps. However, there is a facility for
751        generating tables according to the current locale when PCRE is compiled. It
752        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
753        characters, are recognized by isspace() and therefore were getting set in
754        these tables, and indeed these tables seem to approximate to ISO 8859. This
755        caused a problem in UTF-8 mode when pcre_study() was used to create a list
756        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
757        which of course cannot start UTF-8 characters. I have changed the code so
758        that only real ASCII characters (less than 128) and the correct starting
759        bytes for UTF-8 encodings are set for characters greater than 127 when in
760        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
761        altogether.)
763    20. Added the /T option to pcretest so as to be able to run tests with non-
764        standard character tables, thus making it possible to include the tests
765        used for 19 above in the standard set of tests.
767    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
768        reference to a subpattern the other side of a comment that contains an
769        opening parenthesis caused either an internal compiling error, or a
770        reference to the wrong subpattern.
773  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Removed from v.517  
changed lines
  Added in v.856

  ViewVC Help
Powered by ViewVC 1.1.5