ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 287 by ph10, Tue Dec 18 20:11:28 2007 UTC revision 413 by ph10, Sat Apr 11 11:41:52 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 7.9 11-Apr-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_RECURSION 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.
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.
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.
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().
49    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
50        used for matching.
52    11. Unicode property support in character classes was not working for
53        characters (bytes) greater than 127 when not in UTF-8 mode.
55    12. Added the -M command line option to pcretest.
57    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
59    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
61    16. Added comments and documentation about mis-use of no_arg in the C++
62        wrapper.
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.
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.
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.
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.
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).
90    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
91        heapframe that is used only when UTF-8 support is enabled. This caused no
92        problem, but was untidy.
94    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
95        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
96        included within another project.
98    24. Steven Van Ingelgem's patches to add more options to the CMake support,
99        slightly modified by me:
101          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
102              not building pcregrep.
104          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
105              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
107    25. Forward references, both numeric and by name, in patterns that made use of
108        duplicate group numbers, could behave incorrectly or give incorrect errors,
109        because when scanning forward to find the reference group, PCRE was not
110        taking into account the duplicate group numbers. A pattern such as
111        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
113    26. Changed a few more instances of "const unsigned char *" to USPTR, making
114        the feature of a custom pointer more persuasive (as requested by a user).
116    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
117        pcretest.c, inside #ifndefs, because it seems they are sometimes already
118        pre-defined.
120    28. Added support for (*UTF8) at the start of a pattern.
122    29. Arrange for flags added by the "release type" setting in CMake to be shown
123        in the configuration summary.
126    Version 7.8 05-Sep-08
127    ---------------------
129    1.  Replaced UCP searching code with optimized version as implemented for Ad
130        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
131        stage table and inline lookup instead of a function, giving speed ups of 2
132        to 5 times on some simple patterns that I tested. Permission was given to
133        distribute the MultiStage2.py script that generates the tables (it's not in
134        the tarball, but is in the Subversion repository).
136    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
137        scripts.
139    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
140        a group with a zero qualifier. The result of the study could be incorrect,
141        or the function might crash, depending on the pattern.
143    4.  Caseless matching was not working for non-ASCII characters in back
144        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
145        It now works when Unicode Property Support is available.
147    5.  In pcretest, an escape such as \x{de} in the data was always generating
148        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
149        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
150        truncation.
152    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
154    7.  Added two (int) casts to pcregrep when printing the difference of two
155        pointers, in case they are 64-bit values.
157    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
158        test 2 if it fails.
160    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
161        and a #define of that name to empty if it is not externally set. This is to
162        allow users of MSVC to set it if necessary.
164    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
165        the convenience functions in the pcre_get.c source file.
167    11. An option change at the start of a pattern that had top-level alternatives
168        could cause overwriting and/or a crash. This command provoked a crash in
169        some environments:
171          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
173        This potential security problem was recorded as CVE-2008-2371.
175    12. For a pattern where the match had to start at the beginning or immediately
176        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
177        pcre_dfa_exec() could read past the end of the passed subject if there was
178        no match. To help with detecting such bugs (e.g. with valgrind), I modified
179        pcretest so that it places the subject at the end of its malloc-ed buffer.
181    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
182        exec() might read past the end of the data buffer in UTF-8 mode.
184    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
185        the data contained the byte 0x85 as part of a UTF-8 character within its
186        first line. This applied both to normal and DFA matching.
188    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
189        /^[^d]*?$/8 failed to match "abc".
191    16. Added a missing copyright notice to pcrecpp_internal.h.
193    17. Make it more clear in the documentation that values returned from
194        pcre_exec() in ovector are byte offsets, not character counts.
196    18. Tidied a few places to stop certain compilers from issuing warnings.
198    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
199        supplied by Stefan Weber. I made a further small update for 7.8 because
200        there is a change of source arrangements: the pcre_searchfuncs.c module is
201        replaced by pcre_ucd.c.
204    Version 7.7 07-May-08
205    ---------------------
207    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
208        a string to a long long, pretend we don't even have a long long." This is
209        done by checking for the strtoq, strtoll, and _strtoi64 functions.
211    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
212        pre-7.6 versions, which defined a global no_arg variable instead of putting
213        it in the RE class. (See also #8 below.)
215    3.  Remove a line of dead code, identified by coverity and reported by Nuno
216        Lopes.
218    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
220        (1) The include/exclude patterns were being applied to the whole pathnames
221            of files, instead of just to the final components.
223        (2) If there was more than one level of directory, the subdirectories were
224            skipped unless they satisfied the include/exclude conditions. This is
225            inconsistent with GNU grep (and could even be seen as contrary to the
226            pcregrep specification - which I improved to make it absolutely clear).
227            The action now is always to scan all levels of directory, and just
228            apply the include/exclude patterns to regular files.
230    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
231        --exclude_dir in the tests to avoid scanning .svn directories.
233    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
234        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
235        doesn't support NULs in patterns.
237    7.  Added some missing "const"s to declarations of static tables in
238        pcre_compile.c and pcre_dfa_exec.c.
240    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
241        caused by fix #2  above. (Subsequently also a second patch to fix the
242        first patch. And a third patch - this was a messy problem.)
244    9.  Applied Craig's patch to remove the use of push_back().
246    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
247        matching function regexec().
249    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
250        which, however, unlike Perl's \g{...}, are subroutine calls, not back
251        references. PCRE supports relative numbers with this syntax (I don't think
252        Oniguruma does).
254    12. Previously, a group with a zero repeat such as (...){0} was completely
255        omitted from the compiled regex. However, this means that if the group
256        was called as a subroutine from elsewhere in the pattern, things went wrong
257        (an internal error was given). Such groups are now left in the compiled
258        pattern, with a new opcode that causes them to be skipped at execution
259        time.
261    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
262        to the way PCRE behaves:
264        (a) A lone ] character is dis-allowed (Perl treats it as data).
266        (b) A back reference to an unmatched subpattern matches an empty string
267            (Perl fails the current match path).
269        (c) A data ] in a character class must be notated as \] because if the
270            first data character in a class is ], it defines an empty class. (In
271            Perl it is not possible to have an empty class.) The empty class []
272            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
273            The negative empty class [^] matches any one character, independently
274            of the DOTALL setting.
276    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
277        non-existent subpattern following a character class starting with ']' and
278        containing () gave an internal compiling error instead of "reference to
279        non-existent subpattern". Fortunately, when the pattern did exist, the
280        compiled code was correct. (When scanning forwards to check for the
281        existencd of the subpattern, it was treating the data ']' as terminating
282        the class, so got the count wrong. When actually compiling, the reference
283        was subsequently set up correctly.)
285    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
286        it was being rejected as not supported by pcre_dfa_exec(), even though
287        other assertions are supported. I have made pcre_dfa_exec() support
288        (*FAIL).
290    16. The implementation of 13c above involved the invention of a new opcode,
291        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
292        cannot be changed at match time, I realized I could make a small
293        improvement to matching performance by compiling OP_ALLANY instead of
294        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
295        on the OP_ANY path.
297    17. Compiling pcretest on Windows with readline support failed without the
298        following two fixes: (1) Make the unistd.h include conditional on
299        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
301    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
302        ncurses library to be included for pcretest when ReadLine support is
303        requested, but also to allow for it to be overridden. This patch came from
304        Daniel Bergström.
306    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
307        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
308        any errors with the current Unicode tables. Thanks to Peter Kankowski for
309        spotting this.
312    Version 7.6 28-Jan-08
313    ---------------------
315    1.  A character class containing a very large number of characters with
316        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
317        overflow.
319    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
320        HAVE_LONG_LONG is not defined.
322    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
323        bring them up to date and include new features. This patch includes:
325        - Fixed PH's badly added libz and libbz2 support.
326        - Fixed a problem with static linking.
327        - Added pcredemo. [But later removed - see 7 below.]
328        - Fixed dftables problem and added an option.
329        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
330            HAVE_LONG_LONG.
331        - Added readline support for pcretest.
332        - Added an listing of the option settings after cmake has run.
334    4.  A user submitted a patch to Makefile that makes it easy to create
335        "pcre.dll" under mingw when using Configure/Make. I added stuff to
336        Makefile.am that cause it to include this special target, without
337        affecting anything else. Note that the same mingw target plus all
338        the other distribution libraries and programs are now supported
339        when configuring with CMake (see 6 below) instead of with
340        Configure/Make.
342    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
343        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
344        exported in the Windows port". It has not yet been confirmed that the patch
345        solves the problem, but it does no harm.
347    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
348        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
349        with CMake, and also correct the comment about stack recursion.
351    7.  Remove the automatic building of pcredemo from the ./configure system and
352        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
353        of a program that users should build themselves after PCRE is installed, so
354        building it automatically is not really right. What is more, it gave
355        trouble in some build environments.
357    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
360    Version 7.5 10-Jan-08
361  ---------------------  ---------------------
363  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 76  Version 7.5 12-Nov-07 Line 432  Version 7.5 12-Nov-07
432      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
433      non-matching lines.      non-matching lines.
435  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
437    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
438      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
439      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
440      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
442  15. Fixed two typos in the Windows-only code in pcregrep.c, and moved the  16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
443      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
444      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
446  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
447      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
448      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
449      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that      are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
450      caused the error; without that there was no problem.      caused the error; without that there was no problem.
452  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
454    19. Added --enable-pcretest-libreadline.
456    20. In pcrecpp.cc, the variable 'count' was incremented twice in
457        RE::GlobalReplace(). As a result, the number of replacements returned was
458        double what it should be. I removed one of the increments, but Craig sent a
459        later patch that removed the other one (the right fix) and added unit tests
460        that check the return values (which was not done before).
462    21. Several CMake things:
464        (1) Arranged that, when cmake is used on Unix, the libraries end up with
465            the names libpcre and libpcreposix, not just pcre and pcreposix.
467        (2) The above change means that pcretest and pcregrep are now correctly
468            linked with the newly-built libraries, not previously installed ones.
472    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
473        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
474        UTF-8 newline character). The key issue is that the pattern starts .*;
475        this means that the match must be either at the beginning, or after a
476        newline. The bug was in the code for advancing after a failed match and
477        checking that the new position followed a newline. It was not taking
478        account of UTF-8 characters correctly.
480    23. PCRE was behaving differently from Perl in the way it recognized POSIX
481        character classes. PCRE was not treating the sequence [:...:] as a
482        character class unless the ... were all letters. Perl, however, seems to
483        allow any characters between [: and :], though of course it rejects as
484        unknown any "names" that contain non-letters, because all the known class
485        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
486        for example, whereas PCRE did not - it did not recognize a POSIX character
487        class. This seemed a bit dangerous, so the code has been changed to be
488        closer to Perl. The behaviour is not identical to Perl, because PCRE will
489        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
490        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
491        Perl does, and where it didn't before.
493  18. Added --enable-pcretest-libreadline.  24. Rewrite so as to remove the single use of %n from pcregrep because in some
494        Windows environments %n is disabled by default.
497  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.287  
changed lines
  Added in v.413

  ViewVC Help
Powered by ViewVC 1.1.5