/[pcre]/code/branches/pcre16/ChangeLog
ViewVC logotype

Diff of /code/branches/pcre16/ChangeLog

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

revision 588 by ph10, Sat Jan 15 11:22:47 2011 UTC revision 608 by ph10, Sun Jun 12 16:25:55 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.15 12-Jan-2011  Version 8.13 30-Apr-2011
5    ------------------------
6    
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
8    
9    2.  Two minor typos in pcre_internal.h have been fixed.
10    
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
14    
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
23    
24    5.  Comprehensive information about what went wrong is now returned by
25        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
26        as the output vector has at least 2 elements. The offset of the start of
27        the failing character and a reason code are placed in the vector.
28    
29    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
30        now returned is for the first byte of the failing character, instead of the
31        last byte inspected. This is an incompatible change, but I hope it is small
32        enough not to be a problem. It makes the returned offset consistent with
33        pcre_exec() and pcre_dfa_exec().
34    
35    7.  pcretest now gives a text phrase as well as the error number when
36        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
37        failure, the offset and reason code are output.
38    
39    8.  When \R was used with a maximizing quantifier it failed to skip backwards
40        over a \r\n pair if the subsequent match failed. Instead, it just skipped
41        back over a single character (\n). This seems wrong (because it treated the
42        two characters as a single entity when going forwards), conflicts with the
43        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
44        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
45        has been changed.
46    
47    9.  Some internal refactoring has changed the processing so that the handling
48        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
49        time (the PCRE_DOTALL option was changed this way some time ago: version
50        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
51        which was always a bit of a fudge. It also means that there is one less
52        argument for the match() function, which reduces its stack requirements
53        slightly. This change also fixes an incompatibility with Perl: the pattern
54        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
55    
56    10. More internal refactoring has drastically reduced the number of recursive
57        calls to match() for possessively repeated groups such as (abc)++ when
58        using pcre_exec().
59    
60    11. While implementing 10, a number of bugs in the handling of groups were
61        discovered and fixed:
62    
63        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
64        (a|)*(?1) gave a compile-time internal error.
65        ((a|)+)+  did not notice that the outer group could match an empty string.
66        (^a|^)+   was not marked as anchored.
67        (.*a|.*)+ was not marked as matching at start or after a newline.
68    
69    12. Yet more internal refactoring has removed another argument from the match()
70        function. Special calls to this function are now indicated by setting a
71        value in a variable in the "match data" data block.
72    
73    13. Be more explicit in pcre_study() instead of relying on "default" for
74        opcodes that mean there is no starting character; this means that when new
75        ones are added and accidentally left out of pcre_study(), testing should
76        pick them up.
77    
78    14. The -s option of pcretest has been documented for ages as being an old
79        synonym of -m (show memory usage). I have changed it to mean "force study
80        for every regex", that is, assume /S for every regex. This is similar to -i
81        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
82        using it. It makes it easier to run collection of tests with study enabled,
83        and thereby test pcre_study() more easily.
84    
85    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
86        restoration of the capturing data to the outer values was not happening
87        correctly.
88    
89    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
90        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
91        pattern had matched an empty string, and so incorrectly returned a no
92        match.
93    
94    
95    Version 8.12 15-Jan-2011
96  ------------------------  ------------------------
97    
98  1.  Fixed some typos in the markup of the man pages, and wrote a script that  1.  Fixed some typos in the markup of the man pages, and wrote a script that
99      checks for such things as part of the documentation building process.      checks for such things as part of the documentation building process.
100    
101  2.  On a big-endian 64-bit system, pcregrep did not correctly process the  2.  On a big-endian 64-bit system, pcregrep did not correctly process the
102      --match-limit and --recursion-limit options (added for 8.11). In      --match-limit and --recursion-limit options (added for 8.11). In
103      particular, this made one of the standard tests fail. (The integer value      particular, this made one of the standard tests fail. (The integer value
104      went into the wrong half of a long int.)      went into the wrong half of a long int.)
105    
106  3.  If the --colour option was given to pcregrep with -v (invert match), it  3.  If the --colour option was given to pcregrep with -v (invert match), it
107      did strange things, either producing crazy output, or crashing. It should,      did strange things, either producing crazy output, or crashing. It should,
108      of course, ignore a request for colour when reporting lines that do not      of course, ignore a request for colour when reporting lines that do not
109      match.      match.
110    
111  4.  Another pcregrep bug caused similar problems if --colour was specified with  4.  Another pcregrep bug caused similar problems if --colour was specified with
112      -M (multiline) and the pattern match finished with a line ending.      -M (multiline) and the pattern match finished with a line ending.
113    
114  5.  In pcregrep, when a pattern that ended with a literal newline sequence was  5.  In pcregrep, when a pattern that ended with a literal newline sequence was
115      matched in multiline mode, the following line was shown as part of the      matched in multiline mode, the following line was shown as part of the
116      match. This seems wrong, so I have changed it.      match. This seems wrong, so I have changed it.
117    
118  6.  Another pcregrep bug in multiline mode, when --colour was specified, caused  6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
119      the check for further matches in the same line (so they could be coloured)      the check for further matches in the same line (so they could be coloured)
120      to overrun the end of the current line. If another match was found, it was      to overrun the end of the current line. If another match was found, it was
121      incorrectly shown (and then shown again when found in the next line).      incorrectly shown (and then shown again when found in the next line).
122    
123  7.  If pcregrep was compiled under Windows, there was a reference to the  7.  If pcregrep was compiled under Windows, there was a reference to the
124      function pcregrep_exit() before it was defined. I am assuming this was      function pcregrep_exit() before it was defined. I am assuming this was
125      the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was      the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
126      reported by a user. I've moved the definition above the reference.      reported by a user. I've moved the definition above the reference.
127    
128    
129  Version 8.11 10-Dec-2010  Version 8.11 10-Dec-2010
130  ------------------------  ------------------------

Legend:
Removed from v.588  
changed lines
  Added in v.608

  ViewVC Help
Powered by ViewVC 1.1.5