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

Diff of /code/trunk/ChangeLog

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

revision 260 by ph10, Thu Sep 20 10:19:16 2007 UTC revision 400 by ph10, Sat Mar 21 16:59:40 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4    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 whose
46        condition was an assertion, PCRE could crash during matching, both with
47        pcre_exec() and pcre_dfa_exec().
48    
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
51    
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
54    
55    12. Added the -M command line option to pcretest.
56    
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
58    
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
60    
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
63    
64    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
65        from Martin Jerabek that uses macro names for all relevant character and
66        string constants.
67    
68    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
69        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
70        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
71        these, but not everybody uses configure.
72    
73    19. A conditional group that had only one branch was not being correctly
74        recognized as an item that could match an empty string. This meant that an
75        enclosing group might also not be so recognized, causing infinite looping
76        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
77        with the subject "ab", where knowledge that the repeated group can match
78        nothing is needed in order to break the loop.
79    
80    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
81        exec(), but without supplying a callout function, matching went wrong.
82    
83    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
84        leak if the size of the offset vector was greater than 30. When the vector
85        is smaller, the saved offsets during recursion go onto a local stack
86        vector, but for larger vectors malloc() is used. It was failing to free
87        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
88        error, in fact).
89    
90    
91    Version 7.8 05-Sep-08
92    ---------------------
93    
94    1.  Replaced UCP searching code with optimized version as implemented for Ad
95        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
96        stage table and inline lookup instead of a function, giving speed ups of 2
97        to 5 times on some simple patterns that I tested. Permission was given to
98        distribute the MultiStage2.py script that generates the tables (it's not in
99        the tarball, but is in the Subversion repository).
100    
101    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
102        scripts.
103    
104    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
105        a group with a zero qualifier. The result of the study could be incorrect,
106        or the function might crash, depending on the pattern.
107    
108    4.  Caseless matching was not working for non-ASCII characters in back
109        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
110        It now works when Unicode Property Support is available.
111    
112    5.  In pcretest, an escape such as \x{de} in the data was always generating
113        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
114        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
115        truncation.
116    
117    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
118    
119    7.  Added two (int) casts to pcregrep when printing the difference of two
120        pointers, in case they are 64-bit values.
121    
122    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
123        test 2 if it fails.
124    
125    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
126        and a #define of that name to empty if it is not externally set. This is to
127        allow users of MSVC to set it if necessary.
128    
129    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
130        the convenience functions in the pcre_get.c source file.
131    
132    11. An option change at the start of a pattern that had top-level alternatives
133        could cause overwriting and/or a crash. This command provoked a crash in
134        some environments:
135    
136          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
137    
138        This potential security problem was recorded as CVE-2008-2371.
139    
140    12. For a pattern where the match had to start at the beginning or immediately
141        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
142        pcre_dfa_exec() could read past the end of the passed subject if there was
143        no match. To help with detecting such bugs (e.g. with valgrind), I modified
144        pcretest so that it places the subject at the end of its malloc-ed buffer.
145    
146    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
147        exec() might read past the end of the data buffer in UTF-8 mode.
148    
149    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
150        the data contained the byte 0x85 as part of a UTF-8 character within its
151        first line. This applied both to normal and DFA matching.
152    
153    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
154        /^[^d]*?$/8 failed to match "abc".
155    
156    16. Added a missing copyright notice to pcrecpp_internal.h.
157    
158    17. Make it more clear in the documentation that values returned from
159        pcre_exec() in ovector are byte offsets, not character counts.
160    
161    18. Tidied a few places to stop certain compilers from issuing warnings.
162    
163    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
164        supplied by Stefan Weber. I made a further small update for 7.8 because
165        there is a change of source arrangements: the pcre_searchfuncs.c module is
166        replaced by pcre_ucd.c.
167    
168    
169    Version 7.7 07-May-08
170    ---------------------
171    
172    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
173        a string to a long long, pretend we don't even have a long long." This is
174        done by checking for the strtoq, strtoll, and _strtoi64 functions.
175    
176    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
177        pre-7.6 versions, which defined a global no_arg variable instead of putting
178        it in the RE class. (See also #8 below.)
179    
180    3.  Remove a line of dead code, identified by coverity and reported by Nuno
181        Lopes.
182    
183    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
184    
185        (1) The include/exclude patterns were being applied to the whole pathnames
186            of files, instead of just to the final components.
187    
188        (2) If there was more than one level of directory, the subdirectories were
189            skipped unless they satisfied the include/exclude conditions. This is
190            inconsistent with GNU grep (and could even be seen as contrary to the
191            pcregrep specification - which I improved to make it absolutely clear).
192            The action now is always to scan all levels of directory, and just
193            apply the include/exclude patterns to regular files.
194    
195    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
196        --exclude_dir in the tests to avoid scanning .svn directories.
197    
198    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
199        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
200        doesn't support NULs in patterns.
201    
202    7.  Added some missing "const"s to declarations of static tables in
203        pcre_compile.c and pcre_dfa_exec.c.
204    
205    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
206        caused by fix #2  above. (Subsequently also a second patch to fix the
207        first patch. And a third patch - this was a messy problem.)
208    
209    9.  Applied Craig's patch to remove the use of push_back().
210    
211    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
212        matching function regexec().
213    
214    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
215        which, however, unlike Perl's \g{...}, are subroutine calls, not back
216        references. PCRE supports relative numbers with this syntax (I don't think
217        Oniguruma does).
218    
219    12. Previously, a group with a zero repeat such as (...){0} was completely
220        omitted from the compiled regex. However, this means that if the group
221        was called as a subroutine from elsewhere in the pattern, things went wrong
222        (an internal error was given). Such groups are now left in the compiled
223        pattern, with a new opcode that causes them to be skipped at execution
224        time.
225    
226    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
227        to the way PCRE behaves:
228    
229        (a) A lone ] character is dis-allowed (Perl treats it as data).
230    
231        (b) A back reference to an unmatched subpattern matches an empty string
232            (Perl fails the current match path).
233    
234        (c) A data ] in a character class must be notated as \] because if the
235            first data character in a class is ], it defines an empty class. (In
236            Perl it is not possible to have an empty class.) The empty class []
237            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
238            The negative empty class [^] matches any one character, independently
239            of the DOTALL setting.
240    
241    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
242        non-existent subpattern following a character class starting with ']' and
243        containing () gave an internal compiling error instead of "reference to
244        non-existent subpattern". Fortunately, when the pattern did exist, the
245        compiled code was correct. (When scanning forwards to check for the
246        existencd of the subpattern, it was treating the data ']' as terminating
247        the class, so got the count wrong. When actually compiling, the reference
248        was subsequently set up correctly.)
249    
250    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
251        it was being rejected as not supported by pcre_dfa_exec(), even though
252        other assertions are supported. I have made pcre_dfa_exec() support
253        (*FAIL).
254    
255    16. The implementation of 13c above involved the invention of a new opcode,
256        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
257        cannot be changed at match time, I realized I could make a small
258        improvement to matching performance by compiling OP_ALLANY instead of
259        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
260        on the OP_ANY path.
261    
262    17. Compiling pcretest on Windows with readline support failed without the
263        following two fixes: (1) Make the unistd.h include conditional on
264        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
265    
266    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
267        ncurses library to be included for pcretest when ReadLine support is
268        requested, but also to allow for it to be overridden. This patch came from
269        Daniel Bergström.
270    
271    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
272        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
273        any errors with the current Unicode tables. Thanks to Peter Kankowski for
274        spotting this.
275    
276    
277    Version 7.6 28-Jan-08
278    ---------------------
279    
280    1.  A character class containing a very large number of characters with
281        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
282        overflow.
283    
284    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
285        HAVE_LONG_LONG is not defined.
286    
287    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
288        bring them up to date and include new features. This patch includes:
289    
290        - Fixed PH's badly added libz and libbz2 support.
291        - Fixed a problem with static linking.
292        - Added pcredemo. [But later removed - see 7 below.]
293        - Fixed dftables problem and added an option.
294        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
295            HAVE_LONG_LONG.
296        - Added readline support for pcretest.
297        - Added an listing of the option settings after cmake has run.
298    
299    4.  A user submitted a patch to Makefile that makes it easy to create
300        "pcre.dll" under mingw when using Configure/Make. I added stuff to
301        Makefile.am that cause it to include this special target, without
302        affecting anything else. Note that the same mingw target plus all
303        the other distribution libraries and programs are now supported
304        when configuring with CMake (see 6 below) instead of with
305        Configure/Make.
306    
307    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
308        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
309        exported in the Windows port". It has not yet been confirmed that the patch
310        solves the problem, but it does no harm.
311    
312    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
313        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
314        with CMake, and also correct the comment about stack recursion.
315    
316    7.  Remove the automatic building of pcredemo from the ./configure system and
317        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
318        of a program that users should build themselves after PCRE is installed, so
319        building it automatically is not really right. What is more, it gave
320        trouble in some build environments.
321    
322    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
323    
324    
325    Version 7.5 10-Jan-08
326    ---------------------
327    
328    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
329        values in parens when parsing an RE using the C++ wrapper."
330    
331    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
332        Characters greater than 255 were excluded from the class instead of being
333        included.
334    
335    3.  The same bug as (2) above applied to negated POSIX classes such as
336        [:^space:].
337    
338    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
339        defined or documented. It seems to have been a typo for PCRE_STATIC, so
340        I have changed it.
341    
342    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
343        first named subpattern) and a construct such as (?&a) would reference the
344        first named subpattern whose name started with "a" (in other words, the
345        length check was missing). Both these problems are fixed. "Subpattern name
346        expected" is now given for (?&) (a zero-length name), and this patch also
347        makes it give the same error for \k'' (previously it complained that that
348        was a reference to a non-existent subpattern).
349    
350    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
351        this is right because (?- can be followed by option settings as well as by
352        digits. I have, however, made the messages clearer.
353    
354    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
355        than the number used in the conditional) now cause a compile-time error.
356        This is actually not compatible with Perl, which accepts such patterns, but
357        treats the conditional as always being FALSE (as PCRE used to), but it
358        seems to me that giving a diagnostic is better.
359    
360    8.  Change "alphameric" to the more common word "alphanumeric" in comments
361        and messages.
362    
363    9.  Fix two occurrences of "backslash" in comments that should have been
364        "backspace".
365    
366    10. Remove two redundant lines of code that can never be obeyed (their function
367        was moved elsewhere).
368    
369    11. The program that makes PCRE's Unicode character property table had a bug
370        which caused it to generate incorrect table entries for sequences of
371        characters that have the same character type, but are in different scripts.
372        It amalgamated them into a single range, with the script of the first of
373        them. In other words, some characters were in the wrong script. There were
374        thirteen such cases, affecting characters in the following ranges:
375    
376          U+002b0 - U+002c1
377          U+0060c - U+0060d
378          U+0061e - U+00612
379          U+0064b - U+0065e
380          U+0074d - U+0076d
381          U+01800 - U+01805
382          U+01d00 - U+01d77
383          U+01d9b - U+01dbf
384          U+0200b - U+0200f
385          U+030fc - U+030fe
386          U+03260 - U+0327f
387          U+0fb46 - U+0fbb1
388          U+10450 - U+1049d
389    
390    12. The -o option (show only the matching part of a line) for pcregrep was not
391        compatible with GNU grep in that, if there was more than one match in a
392        line, it showed only the first of them. It now behaves in the same way as
393        GNU grep.
394    
395    13. If the -o and -v options were combined for pcregrep, it printed a blank
396        line for every non-matching line. GNU grep prints nothing, and pcregrep now
397        does the same. The return code can be used to tell if there were any
398        non-matching lines.
399    
400    14. Added --file-offsets and --line-offsets to pcregrep.
401    
402    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
403        infinitely looping recursion. The bug was that positive lookaheads were not
404        being skipped when checking for a possible empty match (negative lookaheads
405        and both kinds of lookbehind were skipped).
406    
407    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
408        inclusion of <windows.h> to before rather than after the definition of
409        INVALID_FILE_ATTRIBUTES (patch from David Byron).
410    
411    17. Specifying a possessive quantifier with a specific limit for a Unicode
412        character property caused pcre_compile() to compile bad code, which led at
413        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
414        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
415        caused the error; without that there was no problem.
416    
417    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
418    
419    19. Added --enable-pcretest-libreadline.
420    
421    20. In pcrecpp.cc, the variable 'count' was incremented twice in
422        RE::GlobalReplace(). As a result, the number of replacements returned was
423        double what it should be. I removed one of the increments, but Craig sent a
424        later patch that removed the other one (the right fix) and added unit tests
425        that check the return values (which was not done before).
426    
427    21. Several CMake things:
428    
429        (1) Arranged that, when cmake is used on Unix, the libraries end up with
430            the names libpcre and libpcreposix, not just pcre and pcreposix.
431    
432        (2) The above change means that pcretest and pcregrep are now correctly
433            linked with the newly-built libraries, not previously installed ones.
434    
435        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
436    
437    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
438        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
439        UTF-8 newline character). The key issue is that the pattern starts .*;
440        this means that the match must be either at the beginning, or after a
441        newline. The bug was in the code for advancing after a failed match and
442        checking that the new position followed a newline. It was not taking
443        account of UTF-8 characters correctly.
444    
445    23. PCRE was behaving differently from Perl in the way it recognized POSIX
446        character classes. PCRE was not treating the sequence [:...:] as a
447        character class unless the ... were all letters. Perl, however, seems to
448        allow any characters between [: and :], though of course it rejects as
449        unknown any "names" that contain non-letters, because all the known class
450        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
451        for example, whereas PCRE did not - it did not recognize a POSIX character
452        class. This seemed a bit dangerous, so the code has been changed to be
453        closer to Perl. The behaviour is not identical to Perl, because PCRE will
454        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
455        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
456        Perl does, and where it didn't before.
457    
458    24. Rewrite so as to remove the single use of %n from pcregrep because in some
459        Windows environments %n is disabled by default.
460    
461    
462  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07
463  ---------------------  ---------------------
464    
# Line 72  Version 7.4 21-Sep-07 Line 530  Version 7.4 21-Sep-07
530      and instead check for _strtoi64 explicitly, and avoid the use of snprintf()      and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
531      entirely. This removes changes made in 7 above.      entirely. This removes changes made in 7 above.
532    
533    17. The CMake files have been updated, and there is now more information about
534        building with CMake in the NON-UNIX-USE document.
535    
536    
537  Version 7.3 28-Aug-07  Version 7.3 28-Aug-07
538  ---------------------  ---------------------

Legend:
Removed from v.260  
changed lines
  Added in v.400

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12