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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.489  
changed lines
  Added in v.544

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12