ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 512 by ph10, Tue Mar 30 11:11:52 2010 UTC revision 552 by ph10, Wed Oct 13 10:15:41 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.03 26-Mar-2010  Version 8.11 10-Oct-2010
5    ------------------------
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".
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).
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.)
26    Version 8.10 25-Jun-2010
27  ------------------------  ------------------------
29  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.03 26-Mar-2010 Line 31  Version 8.03 26-Mar-2010
32  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
34    3.  Inside a character class, \B is treated as a literal by default, but
35        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
36        causes the error). The code is unchanged, but I tidied the documentation.
38    4.  Inside a character class, PCRE always treated \R and \X as literals,
39        whereas Perl faults them if its -w option is set. I have changed PCRE so
40        that it faults them when PCRE_EXTRA is set.
42    5.  Added support for \N, which always matches any character other than
43        newline. (It is the same as "." when PCRE_DOTALL is not set.)
45    6.  When compiling pcregrep with newer versions of gcc which may have
46        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
47        declared with attribute warn_unused_result" were given. Just casting the
48        result to (void) does not stop the warnings; a more elaborate fudge is
49        needed. I've used a macro to implement this.
51    7.  Minor change to pcretest.c to avoid a compiler warning.
53    8.  Added four artifical Unicode properties to help with an option to make
54        \s etc use properties (see next item). The new properties are: Xan
55        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
57    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
58        use Unicode properties. (*UCP) at the start of a pattern can be used to set
59        this option. Modified pcretest to add /W to test this facility. Added
60        REG_UCP to make it available via the POSIX interface.
62    10. Added --line-buffered to pcregrep.
64    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
65        studied, and the match started with a letter with a code point greater than
66        127 whose first byte was different to the first byte of the other case of
67        the letter, the other case of this starting letter was not recognized
68        (#976).
70    12. If a pattern that was studied started with a repeated Unicode property
71        test, for example, \p{Nd}+, there was the theoretical possibility of
72        setting up an incorrect bitmap of starting bytes, but fortunately it could
73        not have actually happened in practice until change 8 above was made (it
74        added property types that matched character-matching opcodes).
76    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
77        possible starting bytes for non-anchored patterns.
79    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
80        \R, and also a number of cases that involve Unicode properties, both
81        explicit and implicit when PCRE_UCP is set.
83    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
84        input, it could crash or give wrong results if characters with values
85        greater than 0xc0 were present in the subject string. (Detail: it assumed
86        UTF-8 input when processing these items.)
88    16. Added a lot of (int) casts to avoid compiler warnings in systems where
89        size_t is 64-bit (#991).
91    17. Added a check for running out of memory when PCRE is compiled with
92        --disable-stack-for-recursion (#990).
94    18. If the last data line in a file for pcretest does not have a newline on
95        the end, a newline was missing in the output.
97    19. The default pcre_chartables.c file recognizes only ASCII characters (values
98        less than 128) in its various bitmaps. However, there is a facility for
99        generating tables according to the current locale when PCRE is compiled. It
100        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
101        characters, are recognized by isspace() and therefore were getting set in
102        these tables, and indeed these tables seem to approximate to ISO 8859. This
103        caused a problem in UTF-8 mode when pcre_study() was used to create a list
104        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
105        which of course cannot start UTF-8 characters. I have changed the code so
106        that only real ASCII characters (less than 128) and the correct starting
107        bytes for UTF-8 encodings are set for characters greater than 127 when in
108        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
109        altogether.)
111    20. Added the /T option to pcretest so as to be able to run tests with non-
112        standard character tables, thus making it possible to include the tests
113        used for 19 above in the standard set of tests.
115    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
116        reference to a subpattern the other side of a comment that contains an
117        opening parenthesis caused either an internal compiling error, or a
118        reference to the wrong subpattern.
121  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010
122  ------------------------  ------------------------

Removed from v.512  
changed lines
  Added in v.552

  ViewVC Help
Powered by ViewVC 1.1.5