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

Diff of /code/trunk/ChangeLog

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

revision 346 by ph10, Wed Apr 30 16:35:49 2008 UTC revision 398 by ph10, Fri Mar 20 20:41:29 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, both with pcre_exec() and pcre_dfa_exec().
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    16. Added comments and documentation about mis-use of no_arg in the C++
61        wrapper.
62    
63    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
64        from Martin Jerabek that uses macro names for all relevant character and
65        string constants.
66    
67    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
68        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
69        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
70        these, but not everybody uses configure.
71    
72    19. A conditional group that had only one branch was not being correctly
73        recognized as an item that could match an empty string. This meant that an
74        enclosing group might also not be so recognized, causing infinite looping
75        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
76        with the subject "ab", where knowledge that the repeated group can match
77        nothing is needed in order to break the loop.
78    
79    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
80        exec(), but without supplying a callout function, matching went wrong.
81    
82    
83    Version 7.8 05-Sep-08
84    ---------------------
85    
86    1.  Replaced UCP searching code with optimized version as implemented for Ad
87        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
88        stage table and inline lookup instead of a function, giving speed ups of 2
89        to 5 times on some simple patterns that I tested. Permission was given to
90        distribute the MultiStage2.py script that generates the tables (it's not in
91        the tarball, but is in the Subversion repository).
92    
93    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
94        scripts.
95    
96    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
97        a group with a zero qualifier. The result of the study could be incorrect,
98        or the function might crash, depending on the pattern.
99    
100    4.  Caseless matching was not working for non-ASCII characters in back
101        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
102        It now works when Unicode Property Support is available.
103    
104    5.  In pcretest, an escape such as \x{de} in the data was always generating
105        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
106        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
107        truncation.
108    
109    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
110    
111    7.  Added two (int) casts to pcregrep when printing the difference of two
112        pointers, in case they are 64-bit values.
113    
114    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
115        test 2 if it fails.
116    
117    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
118        and a #define of that name to empty if it is not externally set. This is to
119        allow users of MSVC to set it if necessary.
120    
121    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
122        the convenience functions in the pcre_get.c source file.
123    
124    11. An option change at the start of a pattern that had top-level alternatives
125        could cause overwriting and/or a crash. This command provoked a crash in
126        some environments:
127    
128          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
129    
130        This potential security problem was recorded as CVE-2008-2371.
131    
132    12. For a pattern where the match had to start at the beginning or immediately
133        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
134        pcre_dfa_exec() could read past the end of the passed subject if there was
135        no match. To help with detecting such bugs (e.g. with valgrind), I modified
136        pcretest so that it places the subject at the end of its malloc-ed buffer.
137    
138    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
139        exec() might read past the end of the data buffer in UTF-8 mode.
140    
141    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
142        the data contained the byte 0x85 as part of a UTF-8 character within its
143        first line. This applied both to normal and DFA matching.
144    
145    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
146        /^[^d]*?$/8 failed to match "abc".
147    
148    16. Added a missing copyright notice to pcrecpp_internal.h.
149    
150    17. Make it more clear in the documentation that values returned from
151        pcre_exec() in ovector are byte offsets, not character counts.
152    
153    18. Tidied a few places to stop certain compilers from issuing warnings.
154    
155    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
156        supplied by Stefan Weber. I made a further small update for 7.8 because
157        there is a change of source arrangements: the pcre_searchfuncs.c module is
158        replaced by pcre_ucd.c.
159    
160    
161    Version 7.7 07-May-08
162  ---------------------  ---------------------
163    
164  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 102  Version 7.7 28-Apr-08 Line 259  Version 7.7 28-Apr-08
259      ncurses library to be included for pcretest when ReadLine support is      ncurses library to be included for pcretest when ReadLine support is
260      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
261      Daniel Bergström.      Daniel Bergström.
262    
263  19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined  19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
264      as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused      as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
265      any errors with the current Unicode tables. Thanks to Peter Kankowski for      any errors with the current Unicode tables. Thanks to Peter Kankowski for
266      spotting this.      spotting this.
267    
268    
269  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
Legend:
Removed from v.346  
changed lines
  Added in v.398
webmaster@exim.org
 ViewVC Help
Powered by ViewVC 1.1.12