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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.275  
changed lines
  Added in v.381

  ViewVC Help
Powered by ViewVC 1.1.5