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

Diff of /code/trunk/ChangeLog

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

revision 345 by ph10, Mon Apr 28 15:10:02 2008 UTC revision 389 by ph10, Sun Mar 15 18:24:05 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 28-Apr-08  Version 7.9 xx-xxx-09
5    ---------------------
6    
7    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
8        (pcretest), all targets were linked against these libraries. This included
9        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
10        libraries. This caused unwanted dependencies to be created. This problem
11        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
12        pcretest is linked with readline.
13    
14    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
15        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
16        moved outside it again, because FALSE and TRUE are already defined in AIX,
17        but BOOL is not.
18    
19    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
20        PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
21    
22    4.  The pcregrep documentation said spaces were inserted as well as colons (or
23        hyphens) following file names and line numbers when outputting matching
24        lines. This is not true; no spaces are inserted. I have also clarified the
25        wording for the --colour (or --color) option.
26    
27    5.  In pcregrep, when --colour was used with -o, the list of matching strings
28        was not coloured; this is different to GNU grep, so I have changed it to be
29        the same.
30    
31    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
32        each matching line was coloured. Now it goes on to look for further matches
33        of any of the test patterns, which is the same behaviour as GNU grep.
34    
35    7.  A pattern that could match an empty string could cause pcregrep to loop; it
36        doesn't make sense to accept an empty string match in pcregrep, so I have
37        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
38        seems to be how GNU grep behaves.
39    
40    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
41        start or after a newline", because the conditional assertion was not being
42        correctly handled. The rule now is that both the assertion and what follows
43        in the first alternative must satisfy the test.
44    
45    9.  If auto-callout was enabled in a pattern with a conditional group, PCRE
46        could crash during matching.
47    
48    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
49        used for matching.
50    
51    11. Unicode property support in character classes was not working for
52        characters (bytes) greater than 127 when not in UTF-8 mode.
53    
54    12. Added the -M command line option to pcretest.
55    
56    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
57    
58    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
59    
60    
61    Version 7.8 05-Sep-08
62    ---------------------
63    
64    1.  Replaced UCP searching code with optimized version as implemented for Ad
65        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
66        stage table and inline lookup instead of a function, giving speed ups of 2
67        to 5 times on some simple patterns that I tested. Permission was given to
68        distribute the MultiStage2.py script that generates the tables (it's not in
69        the tarball, but is in the Subversion repository).
70    
71    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
72        scripts.
73    
74    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
75        a group with a zero qualifier. The result of the study could be incorrect,
76        or the function might crash, depending on the pattern.
77    
78    4.  Caseless matching was not working for non-ASCII characters in back
79        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
80        It now works when Unicode Property Support is available.
81    
82    5.  In pcretest, an escape such as \x{de} in the data was always generating
83        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
84        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
85        truncation.
86    
87    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
88    
89    7.  Added two (int) casts to pcregrep when printing the difference of two
90        pointers, in case they are 64-bit values.
91    
92    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
93        test 2 if it fails.
94    
95    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
96        and a #define of that name to empty if it is not externally set. This is to
97        allow users of MSVC to set it if necessary.
98    
99    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
100        the convenience functions in the pcre_get.c source file.
101    
102    11. An option change at the start of a pattern that had top-level alternatives
103        could cause overwriting and/or a crash. This command provoked a crash in
104        some environments:
105    
106          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
107    
108        This potential security problem was recorded as CVE-2008-2371.
109    
110    12. For a pattern where the match had to start at the beginning or immediately
111        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
112        pcre_dfa_exec() could read past the end of the passed subject if there was
113        no match. To help with detecting such bugs (e.g. with valgrind), I modified
114        pcretest so that it places the subject at the end of its malloc-ed buffer.
115    
116    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
117        exec() might read past the end of the data buffer in UTF-8 mode.
118    
119    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
120        the data contained the byte 0x85 as part of a UTF-8 character within its
121        first line. This applied both to normal and DFA matching.
122    
123    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
124        /^[^d]*?$/8 failed to match "abc".
125    
126    16. Added a missing copyright notice to pcrecpp_internal.h.
127    
128    17. Make it more clear in the documentation that values returned from
129        pcre_exec() in ovector are byte offsets, not character counts.
130    
131    18. Tidied a few places to stop certain compilers from issuing warnings.
132    
133    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
134        supplied by Stefan Weber. I made a further small update for 7.8 because
135        there is a change of source arrangements: the pcre_searchfuncs.c module is
136        replaced by pcre_ucd.c.
137    
138    
139    Version 7.7 07-May-08
140  ---------------------  ---------------------
141    
142  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
# Line 103  Version 7.7 28-Apr-08 Line 238  Version 7.7 28-Apr-08
238      requested, but also to allow for it to be overridden. This patch came from      requested, but also to allow for it to be overridden. This patch came from
239      Daniel Bergström.      Daniel Bergström.
240    
241    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
242        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
243        any errors with the current Unicode tables. Thanks to Peter Kankowski for
244        spotting this.
245    
246    
247  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
248  ---------------------  ---------------------

Legend:
Removed from v.345  
changed lines
  Added in v.389

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12