/[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 524 by ph10, Mon May 24 17:06:28 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 8.02 01-Mar-2010  Version 8.10 03 May-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    
47    12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a
48        conflict in the definition of PCRE_EXP_DECL. I have removed the include of
49        pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of
50        historical tidying that never got done.)
51    
52    13. If a pattern that was studied started with a repeated Unicode property
53        test, for example, \p{Nd}+, there was the theoretical possibility of
54        setting up an incorrect bitmap of starting bytes, but fortunately it could
55        not have actually happened in practice until change 8 above was made (it
56        added property types that matched character-matching opcodes).
57    
58    14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
59        possible starting bytes for non-anchored patterns.
60    
61    
62    
63    Version 8.02 19-Mar-2010
64  ------------------------  ------------------------
65    
66  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.
67    
68  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
69      configured.      configured.
70    
71  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
72      original author of that file, following a query about its status.      original author of that file, following a query about its status.
73    
74  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
75      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.
76    
77  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive  5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
78      quantifier applied to a forward-referencing subroutine call, could compile      quantifier applied to a forward-referencing subroutine call, could compile
79      incorrect code or give the error "internal error: previously-checked      incorrect code or give the error "internal error: previously-checked
80      referenced subpattern not found".      referenced subpattern not found".
81    
82  6.  Both MS Visual Studio and Symbian OS have problems with initializing  6.  Both MS Visual Studio and Symbian OS have problems with initializing
83      variables to point to external functions. For these systems, therefore,      variables to point to external functions. For these systems, therefore,
84      pcre_malloc etc. are now initialized to local functions that call the      pcre_malloc etc. are now initialized to local functions that call the
85      relevant global functions.      relevant global functions.
86    
87  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
88      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.
89      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
90      the lengths are correct (equal to the number of opcodes).      the lengths are correct (equal to the number of opcodes).
91    
92  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
93      eint vector in pcreposix.c.      eint vector in pcreposix.c.
94    
95  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
96      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,
97      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,
98      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
99      string.      string.
100    
101  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.
102    
103  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
104      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
105      \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
106      the assertion is positive, but not if it is negative.      the assertion is positive, but not if it is negative.
107    
108  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
109      "match()" function of pcre_exec.c by one pointer. Forthcoming      "match()" function of pcre_exec.c by one pointer. Forthcoming
110      implementation of support for (*MARK) will need an extra pointer on the      implementation of support for (*MARK) will need an extra pointer on the
111      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
112      decrease.      decrease.
113    
114  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
115      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
116      second branch in the above example - was incorrectly given the compile-      second branch in the above example - was incorrectly given the compile-
117      time error "recursive call could loop indefinitely" because pcre_compile()      time error "recursive call could loop indefinitely" because pcre_compile()
118      was not correctly checking the subroutine for matching a non-empty string.      was not correctly checking the subroutine for matching a non-empty string.
119    
120    14. The checks for overrunning compiling workspace could trigger after an
121        overrun had occurred. This is a "should never occur" error, but it can be
122        triggered by pathological patterns such as hundreds of nested parentheses.
123        The checks now trigger 100 bytes before the end of the workspace.
124    
125    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
126    
127    
128  Version 8.01 19-Jan-2010  Version 8.01 19-Jan-2010

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

  ViewVC Help
Powered by ViewVC 1.1.5