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

Diff of /code/trunk/ChangeLog

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

revision 295 by ph10, Mon Dec 31 17:00:24 2007 UTC revision 390 by ph10, Tue Mar 17 10:58:16 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.5 31-Dec-07  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    16. Added comments and documentation about mis-use of no_arg in the C++
61        wrapper.
62    
63    
64    Version 7.8 05-Sep-08
65    ---------------------
66    
67    1.  Replaced UCP searching code with optimized version as implemented for Ad
68        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
69        stage table and inline lookup instead of a function, giving speed ups of 2
70        to 5 times on some simple patterns that I tested. Permission was given to
71        distribute the MultiStage2.py script that generates the tables (it's not in
72        the tarball, but is in the Subversion repository).
73    
74    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
75        scripts.
76    
77    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
78        a group with a zero qualifier. The result of the study could be incorrect,
79        or the function might crash, depending on the pattern.
80    
81    4.  Caseless matching was not working for non-ASCII characters in back
82        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
83        It now works when Unicode Property Support is available.
84    
85    5.  In pcretest, an escape such as \x{de} in the data was always generating
86        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
87        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
88        truncation.
89    
90    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
91    
92    7.  Added two (int) casts to pcregrep when printing the difference of two
93        pointers, in case they are 64-bit values.
94    
95    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
96        test 2 if it fails.
97    
98    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
99        and a #define of that name to empty if it is not externally set. This is to
100        allow users of MSVC to set it if necessary.
101    
102    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
103        the convenience functions in the pcre_get.c source file.
104    
105    11. An option change at the start of a pattern that had top-level alternatives
106        could cause overwriting and/or a crash. This command provoked a crash in
107        some environments:
108    
109          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
110    
111        This potential security problem was recorded as CVE-2008-2371.
112    
113    12. For a pattern where the match had to start at the beginning or immediately
114        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
115        pcre_dfa_exec() could read past the end of the passed subject if there was
116        no match. To help with detecting such bugs (e.g. with valgrind), I modified
117        pcretest so that it places the subject at the end of its malloc-ed buffer.
118    
119    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
120        exec() might read past the end of the data buffer in UTF-8 mode.
121    
122    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
123        the data contained the byte 0x85 as part of a UTF-8 character within its
124        first line. This applied both to normal and DFA matching.
125    
126    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
127        /^[^d]*?$/8 failed to match "abc".
128    
129    16. Added a missing copyright notice to pcrecpp_internal.h.
130    
131    17. Make it more clear in the documentation that values returned from
132        pcre_exec() in ovector are byte offsets, not character counts.
133    
134    18. Tidied a few places to stop certain compilers from issuing warnings.
135    
136    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
137        supplied by Stefan Weber. I made a further small update for 7.8 because
138        there is a change of source arrangements: the pcre_searchfuncs.c module is
139        replaced by pcre_ucd.c.
140    
141    
142    Version 7.7 07-May-08
143    ---------------------
144    
145    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
146        a string to a long long, pretend we don't even have a long long." This is
147        done by checking for the strtoq, strtoll, and _strtoi64 functions.
148    
149    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
150        pre-7.6 versions, which defined a global no_arg variable instead of putting
151        it in the RE class. (See also #8 below.)
152    
153    3.  Remove a line of dead code, identified by coverity and reported by Nuno
154        Lopes.
155    
156    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
157    
158        (1) The include/exclude patterns were being applied to the whole pathnames
159            of files, instead of just to the final components.
160    
161        (2) If there was more than one level of directory, the subdirectories were
162            skipped unless they satisfied the include/exclude conditions. This is
163            inconsistent with GNU grep (and could even be seen as contrary to the
164            pcregrep specification - which I improved to make it absolutely clear).
165            The action now is always to scan all levels of directory, and just
166            apply the include/exclude patterns to regular files.
167    
168    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
169        --exclude_dir in the tests to avoid scanning .svn directories.
170    
171    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
172        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
173        doesn't support NULs in patterns.
174    
175    7.  Added some missing "const"s to declarations of static tables in
176        pcre_compile.c and pcre_dfa_exec.c.
177    
178    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
179        caused by fix #2  above. (Subsequently also a second patch to fix the
180        first patch. And a third patch - this was a messy problem.)
181    
182    9.  Applied Craig's patch to remove the use of push_back().
183    
184    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
185        matching function regexec().
186    
187    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
188        which, however, unlike Perl's \g{...}, are subroutine calls, not back
189        references. PCRE supports relative numbers with this syntax (I don't think
190        Oniguruma does).
191    
192    12. Previously, a group with a zero repeat such as (...){0} was completely
193        omitted from the compiled regex. However, this means that if the group
194        was called as a subroutine from elsewhere in the pattern, things went wrong
195        (an internal error was given). Such groups are now left in the compiled
196        pattern, with a new opcode that causes them to be skipped at execution
197        time.
198    
199    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
200        to the way PCRE behaves:
201    
202        (a) A lone ] character is dis-allowed (Perl treats it as data).
203    
204        (b) A back reference to an unmatched subpattern matches an empty string
205            (Perl fails the current match path).
206    
207        (c) A data ] in a character class must be notated as \] because if the
208            first data character in a class is ], it defines an empty class. (In
209            Perl it is not possible to have an empty class.) The empty class []
210            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
211            The negative empty class [^] matches any one character, independently
212            of the DOTALL setting.
213    
214    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
215        non-existent subpattern following a character class starting with ']' and
216        containing () gave an internal compiling error instead of "reference to
217        non-existent subpattern". Fortunately, when the pattern did exist, the
218        compiled code was correct. (When scanning forwards to check for the
219        existencd of the subpattern, it was treating the data ']' as terminating
220        the class, so got the count wrong. When actually compiling, the reference
221        was subsequently set up correctly.)
222    
223    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
224        it was being rejected as not supported by pcre_dfa_exec(), even though
225        other assertions are supported. I have made pcre_dfa_exec() support
226        (*FAIL).
227    
228    16. The implementation of 13c above involved the invention of a new opcode,
229        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
230        cannot be changed at match time, I realized I could make a small
231        improvement to matching performance by compiling OP_ALLANY instead of
232        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
233        on the OP_ANY path.
234    
235    17. Compiling pcretest on Windows with readline support failed without the
236        following two fixes: (1) Make the unistd.h include conditional on
237        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
238    
239    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
240        ncurses library to be included for pcretest when ReadLine support is
241        requested, but also to allow for it to be overridden. This patch came from
242        Daniel Bergström.
243    
244    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
245        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
246        any errors with the current Unicode tables. Thanks to Peter Kankowski for
247        spotting this.
248    
249    
250    Version 7.6 28-Jan-08
251    ---------------------
252    
253    1.  A character class containing a very large number of characters with
254        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
255        overflow.
256    
257    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
258        HAVE_LONG_LONG is not defined.
259    
260    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
261        bring them up to date and include new features. This patch includes:
262    
263        - Fixed PH's badly added libz and libbz2 support.
264        - Fixed a problem with static linking.
265        - Added pcredemo. [But later removed - see 7 below.]
266        - Fixed dftables problem and added an option.
267        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
268            HAVE_LONG_LONG.
269        - Added readline support for pcretest.
270        - Added an listing of the option settings after cmake has run.
271    
272    4.  A user submitted a patch to Makefile that makes it easy to create
273        "pcre.dll" under mingw when using Configure/Make. I added stuff to
274        Makefile.am that cause it to include this special target, without
275        affecting anything else. Note that the same mingw target plus all
276        the other distribution libraries and programs are now supported
277        when configuring with CMake (see 6 below) instead of with
278        Configure/Make.
279    
280    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
281        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
282        exported in the Windows port". It has not yet been confirmed that the patch
283        solves the problem, but it does no harm.
284    
285    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
286        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
287        with CMake, and also correct the comment about stack recursion.
288    
289    7.  Remove the automatic building of pcredemo from the ./configure system and
290        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
291        of a program that users should build themselves after PCRE is installed, so
292        building it automatically is not really right. What is more, it gave
293        trouble in some build environments.
294    
295    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
296    
297    
298    Version 7.5 10-Jan-08
299  ---------------------  ---------------------
300    
301  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
# Line 99  Version 7.5 31-Dec-07 Line 393  Version 7.5 31-Dec-07
393    
394  20. In pcrecpp.cc, the variable 'count' was incremented twice in  20. In pcrecpp.cc, the variable 'count' was incremented twice in
395      RE::GlobalReplace(). As a result, the number of replacements returned was      RE::GlobalReplace(). As a result, the number of replacements returned was
396      double what it should be. I have removed one of the increments.      double what it should be. I removed one of the increments, but Craig sent a
397        later patch that removed the other one (the right fix) and added unit tests
398        that check the return values (which was not done before).
399    
400  21. Several CMake things:  21. Several CMake things:
401    
# Line 110  Version 7.5 31-Dec-07 Line 406  Version 7.5 31-Dec-07
406          linked with the newly-built libraries, not previously installed ones.          linked with the newly-built libraries, not previously installed ones.
407    
408      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.      (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
409    
410  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*  22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
411      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a      crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
412      UTF-8 newline character). The key issue is that the pattern starts .*;      UTF-8 newline character). The key issue is that the pattern starts .*;
413      this means that the match must be either at the beginning, or after a      this means that the match must be either at the beginning, or after a
414      newline. The bug was in the code for advancing after a failed match and      newline. The bug was in the code for advancing after a failed match and
415      checking that the new position followed a newline. It was not taking      checking that the new position followed a newline. It was not taking
416      account of UTF-8 characters correctly.      account of UTF-8 characters correctly.
417    
418  23. PCRE was behaving differently from Perl in the way it recognized POSIX  23. PCRE was behaving differently from Perl in the way it recognized POSIX
419      character classes. PCRE was not treating the sequence [:...:] as a      character classes. PCRE was not treating the sequence [:...:] as a
420      character class unless the ... were all letters. Perl, however, seems to      character class unless the ... were all letters. Perl, however, seems to
421      allow any characters between [: and :], though of course it rejects as      allow any characters between [: and :], though of course it rejects as
422      unknown any "names" that contain non-letters, because all the known class      unknown any "names" that contain non-letters, because all the known class
423      names consist only of letters. Thus, Perl gives an error for [[:1234:]],      names consist only of letters. Thus, Perl gives an error for [[:1234:]],
424      for example, whereas PCRE did not - it did not recognize a POSIX character      for example, whereas PCRE did not - it did not recognize a POSIX character
425      class. This seemed a bit dangerous, so the code has been changed to be      class. This seemed a bit dangerous, so the code has been changed to be
426      closer to Perl. The behaviour is not identical to Perl, because PCRE will      closer to Perl. The behaviour is not identical to Perl, because PCRE will
427      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will      diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
428      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where      treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
429      Perl does, and where it didn't before.      Perl does, and where it didn't before.
430    
431    24. Rewrite so as to remove the single use of %n from pcregrep because in some
432        Windows environments %n is disabled by default.
433    
434    
435  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Legend:
Removed from v.295  
changed lines
  Added in v.390

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12