/[pcre]/code/trunk/ChangeLog
ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 503 by ph10, Sun Mar 7 17:35:52 2010 UTC revision 553 by ph10, Fri Oct 22 15:57:50 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  Version 8.11 10-Oct-2010
5    ------------------------
6    
7    1.  (*THEN) was not working properly if there were untried alternatives prior
8        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
9        backtracked to try for "b" instead of moving to the next alternative branch
10        at the same level (in this case, to look for "c"). The Perl documentation
11        is clear that when (*THEN) is backtracked onto, it goes to the "next
12        alternative in the innermost enclosing group".
13    
14    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
15        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
16        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
17        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
18        (*THEN).
19    
20    3.  If \s appeared in a character class, it removed the VT character from
21        the class, even if it had been included by some previous item, for example
22        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
23        of \s, but is part of the POSIX "space" class.)
24    
25    4.  A partial match never returns an empty string (because you can always
26        match an empty string at the end of the subject); however the checking for
27        an empty string was starting at the "start of match" point. This has been
28        changed to the "earliest inspected character" point, because the returned
29        data for a partial match starts at this character. This means that, for
30        example, /(?<=abc)def/ gives a partial match for the subject "abc"
31        (previously it gave "no match").
32    
33    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
34        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
35        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
36        has an implication that the given string is incomplete (because a partial
37        match is preferred over a full match). For this reason, these items now
38        give a partial match in this situation. [Aside: previously, the one case
39        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
40        match rather than a full match, which was wrong by the old rules, but is
41        now correct.]
42    
43    
44    Version 8.10 25-Jun-2010
45    ------------------------
46    
47    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
48        THEN.
49    
50    2.  (*ACCEPT) was not working when inside an atomic group.
51    
52    3.  Inside a character class, \B is treated as a literal by default, but
53        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
54        causes the error). The code is unchanged, but I tidied the documentation.
55    
56    4.  Inside a character class, PCRE always treated \R and \X as literals,
57        whereas Perl faults them if its -w option is set. I have changed PCRE so
58        that it faults them when PCRE_EXTRA is set.
59    
60    5.  Added support for \N, which always matches any character other than
61        newline. (It is the same as "." when PCRE_DOTALL is not set.)
62    
63    6.  When compiling pcregrep with newer versions of gcc which may have
64        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
65        declared with attribute warn_unused_result" were given. Just casting the
66        result to (void) does not stop the warnings; a more elaborate fudge is
67        needed. I've used a macro to implement this.
68    
69    7.  Minor change to pcretest.c to avoid a compiler warning.
70    
71    8.  Added four artifical Unicode properties to help with an option to make
72        \s etc use properties (see next item). The new properties are: Xan
73        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
74    
75    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
76        use Unicode properties. (*UCP) at the start of a pattern can be used to set
77        this option. Modified pcretest to add /W to test this facility. Added
78        REG_UCP to make it available via the POSIX interface.
79    
80    10. Added --line-buffered to pcregrep.
81    
82    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
83        studied, and the match started with a letter with a code point greater than
84        127 whose first byte was different to the first byte of the other case of
85        the letter, the other case of this starting letter was not recognized
86        (#976).
87    
88    12. If a pattern that was studied started with a repeated Unicode property
89        test, for example, \p{Nd}+, there was the theoretical possibility of
90        setting up an incorrect bitmap of starting bytes, but fortunately it could
91        not have actually happened in practice until change 8 above was made (it
92        added property types that matched character-matching opcodes).
93    
94    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
95        possible starting bytes for non-anchored patterns.
96    
97    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
98        \R, and also a number of cases that involve Unicode properties, both
99        explicit and implicit when PCRE_UCP is set.
100    
101    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
102        input, it could crash or give wrong results if characters with values
103        greater than 0xc0 were present in the subject string. (Detail: it assumed
104        UTF-8 input when processing these items.)
105    
106    16. Added a lot of (int) casts to avoid compiler warnings in systems where
107        size_t is 64-bit (#991).
108    
109    17. Added a check for running out of memory when PCRE is compiled with
110        --disable-stack-for-recursion (#990).
111    
112    18. If the last data line in a file for pcretest does not have a newline on
113        the end, a newline was missing in the output.
114    
115    19. The default pcre_chartables.c file recognizes only ASCII characters (values
116        less than 128) in its various bitmaps. However, there is a facility for
117        generating tables according to the current locale when PCRE is compiled. It
118        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
119        characters, are recognized by isspace() and therefore were getting set in
120        these tables, and indeed these tables seem to approximate to ISO 8859. This
121        caused a problem in UTF-8 mode when pcre_study() was used to create a list
122        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
123        which of course cannot start UTF-8 characters. I have changed the code so
124        that only real ASCII characters (less than 128) and the correct starting
125        bytes for UTF-8 encodings are set for characters greater than 127 when in
126        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
127        altogether.)
128    
129    20. Added the /T option to pcretest so as to be able to run tests with non-
130        standard character tables, thus making it possible to include the tests
131        used for 19 above in the standard set of tests.
132    
133    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
134        reference to a subpattern the other side of a comment that contains an
135        opening parenthesis caused either an internal compiling error, or a
136        reference to the wrong subpattern.
137    
138    
139    Version 8.02 19-Mar-2010
140  ------------------------  ------------------------
141    
142  1.  The Unicode data tables have been updated to Unicode 5.2.0.  1.  The Unicode data tables have been updated to Unicode 5.2.0.
143    
144  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is  2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
145      configured.      configured.
146    
147  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the  3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
148      original author of that file, following a query about its status.      original author of that file, following a query about its status.
149    
150  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include  4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
151      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.      inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
152    
153  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
154      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
155      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
156      referenced subpattern not found".      referenced subpattern not found".
157    
158  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
159      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
160      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
161      relevant global functions.      relevant global functions.
162    
163  7.  There were two entries missing in the vectors called coptable and poptable  7.  There were two entries missing in the vectors called coptable and poptable
164      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.      in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
165      I've fixed the data, and added a kludgy way of testing at compile time that      I've fixed the data, and added a kludgy way of testing at compile time that
166      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
167    
168  8.  Following on from 7, I added a similar kludge to check the length of the  8.  Following on from 7, I added a similar kludge to check the length of the
169      eint vector in pcreposix.c.      eint vector in pcreposix.c.
170    
171  9.  Error texts for pcre_compile() are held as one long string to avoid too  9.  Error texts for pcre_compile() are held as one long string to avoid too
172      much relocation at load time. To find a text, the string is searched,      much relocation at load time. To find a text, the string is searched,
173      counting zeros. There was no check for running off the end of the string,      counting zeros. There was no check for running off the end of the string,
174      which could happen if a new error number was added without updating the      which could happen if a new error number was added without updating the
175      string.      string.
176    
177  10. \K gave a compile-time error if it appeared in a lookbehind assersion.  10. \K gave a compile-time error if it appeared in a lookbehind assersion.
178    
179  11. \K was not working if it appeared in an atomic group or in a group that  11. \K was not working if it appeared in an atomic group or in a group that
180      was called as a "subroutine", or in an assertion. Perl 5.11 documents that      was called as a "subroutine", or in an assertion. Perl 5.11 documents that
181      \K is "not well defined" if used in an assertion. PCRE now accepts it if      \K is "not well defined" if used in an assertion. PCRE now accepts it if
182      the assertion is positive, but not if it is negative.      the assertion is positive, but not if it is negative.
183    
184  12. Change 11 fortuitously reduced the size of the stack frame used in the  12. Change 11 fortuitously reduced the size of the stack frame used in the
185      "match()" function of pcre_exec.c by one pointer. Forthcoming      "match()" function of pcre_exec.c by one pointer. Forthcoming
186      implementation of support for (*MARK) will need an extra pointer on the      implementation of support for (*MARK) will need an extra pointer on the
187      stack; I have reserved it now, so that the stack frame size does not      stack; I have reserved it now, so that the stack frame size does not
188      decrease.      decrease.
189    
190  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other  13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
191      item in branch that calls a recursion is a subroutine call - as in the      item in branch that calls a recursion is a subroutine call - as in the
192      second branch in the above example - was incorrectly given the compile-      second branch in the above example - was incorrectly given the compile-
193      time error "recursive call could loop indefinitely" because pcre_compile()      time error "recursive call could loop indefinitely" because pcre_compile()
194      was not correctly checking the subroutine for matching a non-empty string.      was not correctly checking the subroutine for matching a non-empty string.
195    
196    14. The checks for overrunning compiling workspace could trigger after an
197        overrun had occurred. This is a "should never occur" error, but it can be
198        triggered by pathological patterns such as hundreds of nested parentheses.
199        The checks now trigger 100 bytes before the end of the workspace.
200    
201    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
202    
203    
204  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010

Legend:
Removed from v.503  
changed lines
  Added in v.553

  ViewVC Help
Powered by ViewVC 1.1.5