ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.269  
changed lines
  Added in v.378

  ViewVC Help
Powered by ViewVC 1.1.5