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 422 by ph10, Fri Aug 14 16:42:55 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.00 ??-???-??
5    ----------------------
7    1.  The table for translating pcre_compile() error codes into POSIX error codes
8        was out-of-date, and there was no check on the pcre_compile() error code
9        being within the table. This could lead to an OK return being given in
10        error.
12    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
13        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
14        in a Windows environment.
16    3.  The pcregrep --count option prints the count for each file even when it is
17        zero, as does GNU grep. However, pcregrep was also printing all files when
18        --files-with-matches was added. Now, when both options are given, it prints
19        counts only for those files that have at least one match. (GNU grep just
20        prints the file name in this circumstance, but including the count seems
21        more useful - otherwise, why use --count?) Also ensured that the
22        combination -clh just lists non-zero counts, with no names.
24    4.  The long form of the pcregrep -F option was incorrectly implemented as
25        --fixed_strings instead of --fixed-strings. This is an incompatible change,
26        but it seems right to fix it, and I didn't think it was worth preserving
27        the old behaviour.
29    5.  The command line items --regex=pattern and --regexp=pattern were not
30        recognized by pcregrep, which required --regex pattern or --regexp pattern
31        (with a space rather than an '='). The man page documented the '=' forms,
32        which are compatible with GNU grep; these now work.
35    Version 7.9 11-Apr-09
36    ---------------------
38    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
39        (pcretest), all targets were linked against these libraries. This included
40        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
41        libraries. This caused unwanted dependencies to be created. This problem
42        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
43        pcretest is linked with readline.
45    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
46        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
47        moved outside it again, because FALSE and TRUE are already defined in AIX,
48        but BOOL is not.
50    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
51        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
53    4.  The pcregrep documentation said spaces were inserted as well as colons (or
54        hyphens) following file names and line numbers when outputting matching
55        lines. This is not true; no spaces are inserted. I have also clarified the
56        wording for the --colour (or --color) option.
58    5.  In pcregrep, when --colour was used with -o, the list of matching strings
59        was not coloured; this is different to GNU grep, so I have changed it to be
60        the same.
62    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
63        each matching line was coloured. Now it goes on to look for further matches
64        of any of the test patterns, which is the same behaviour as GNU grep.
66    7.  A pattern that could match an empty string could cause pcregrep to loop; it
67        doesn't make sense to accept an empty string match in pcregrep, so I have
68        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
69        seems to be how GNU grep behaves.
71    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
72        start or after a newline", because the conditional assertion was not being
73        correctly handled. The rule now is that both the assertion and what follows
74        in the first alternative must satisfy the test.
76    9.  If auto-callout was enabled in a pattern with a conditional group whose
77        condition was an assertion, PCRE could crash during matching, both with
78        pcre_exec() and pcre_dfa_exec().
80    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
81        used for matching.
83    11. Unicode property support in character classes was not working for
84        characters (bytes) greater than 127 when not in UTF-8 mode.
86    12. Added the -M command line option to pcretest.
88    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
90    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
92    16. Added comments and documentation about mis-use of no_arg in the C++
93        wrapper.
95    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
96        from Martin Jerabek that uses macro names for all relevant character and
97        string constants.
99    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
100        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
101        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
102        these, but not everybody uses configure.
104    19. A conditional group that had only one branch was not being correctly
105        recognized as an item that could match an empty string. This meant that an
106        enclosing group might also not be so recognized, causing infinite looping
107        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
108        with the subject "ab", where knowledge that the repeated group can match
109        nothing is needed in order to break the loop.
111    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
112        exec(), but without supplying a callout function, matching went wrong.
114    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
115        leak if the size of the offset vector was greater than 30. When the vector
116        is smaller, the saved offsets during recursion go onto a local stack
117        vector, but for larger vectors malloc() is used. It was failing to free
118        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
119        error, in fact).
121    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
122        heapframe that is used only when UTF-8 support is enabled. This caused no
123        problem, but was untidy.
125    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
126        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
127        included within another project.
129    24. Steven Van Ingelgem's patches to add more options to the CMake support,
130        slightly modified by me:
132          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
133              not building pcregrep.
135          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
136              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
138    25. Forward references, both numeric and by name, in patterns that made use of
139        duplicate group numbers, could behave incorrectly or give incorrect errors,
140        because when scanning forward to find the reference group, PCRE was not
141        taking into account the duplicate group numbers. A pattern such as
142        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
144    26. Changed a few more instances of "const unsigned char *" to USPTR, making
145        the feature of a custom pointer more persuasive (as requested by a user).
147    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
148        pcretest.c, inside #ifndefs, because it seems they are sometimes already
149        pre-defined.
151    28. Added support for (*UTF8) at the start of a pattern.
153    29. Arrange for flags added by the "release type" setting in CMake to be shown
154        in the configuration summary.
157    Version 7.8 05-Sep-08
158    ---------------------
160    1.  Replaced UCP searching code with optimized version as implemented for Ad
161        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
162        stage table and inline lookup instead of a function, giving speed ups of 2
163        to 5 times on some simple patterns that I tested. Permission was given to
164        distribute the MultiStage2.py script that generates the tables (it's not in
165        the tarball, but is in the Subversion repository).
167    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
168        scripts.
170    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
171        a group with a zero qualifier. The result of the study could be incorrect,
172        or the function might crash, depending on the pattern.
174    4.  Caseless matching was not working for non-ASCII characters in back
175        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
176        It now works when Unicode Property Support is available.
178    5.  In pcretest, an escape such as \x{de} in the data was always generating
179        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
180        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
181        truncation.
183    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
185    7.  Added two (int) casts to pcregrep when printing the difference of two
186        pointers, in case they are 64-bit values.
188    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
189        test 2 if it fails.
191    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
192        and a #define of that name to empty if it is not externally set. This is to
193        allow users of MSVC to set it if necessary.
195    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
196        the convenience functions in the pcre_get.c source file.
198    11. An option change at the start of a pattern that had top-level alternatives
199        could cause overwriting and/or a crash. This command provoked a crash in
200        some environments:
202          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
204        This potential security problem was recorded as CVE-2008-2371.
206    12. For a pattern where the match had to start at the beginning or immediately
207        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
208        pcre_dfa_exec() could read past the end of the passed subject if there was
209        no match. To help with detecting such bugs (e.g. with valgrind), I modified
210        pcretest so that it places the subject at the end of its malloc-ed buffer.
212    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
213        exec() might read past the end of the data buffer in UTF-8 mode.
215    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
216        the data contained the byte 0x85 as part of a UTF-8 character within its
217        first line. This applied both to normal and DFA matching.
219    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
220        /^[^d]*?$/8 failed to match "abc".
222    16. Added a missing copyright notice to pcrecpp_internal.h.
224    17. Make it more clear in the documentation that values returned from
225        pcre_exec() in ovector are byte offsets, not character counts.
227    18. Tidied a few places to stop certain compilers from issuing warnings.
229    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
230        supplied by Stefan Weber. I made a further small update for 7.8 because
231        there is a change of source arrangements: the pcre_searchfuncs.c module is
232        replaced by pcre_ucd.c.
235    Version 7.7 07-May-08
236    ---------------------
238    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
239        a string to a long long, pretend we don't even have a long long." This is
240        done by checking for the strtoq, strtoll, and _strtoi64 functions.
242    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
243        pre-7.6 versions, which defined a global no_arg variable instead of putting
244        it in the RE class. (See also #8 below.)
246    3.  Remove a line of dead code, identified by coverity and reported by Nuno
247        Lopes.
249    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
251        (1) The include/exclude patterns were being applied to the whole pathnames
252            of files, instead of just to the final components.
254        (2) If there was more than one level of directory, the subdirectories were
255            skipped unless they satisfied the include/exclude conditions. This is
256            inconsistent with GNU grep (and could even be seen as contrary to the
257            pcregrep specification - which I improved to make it absolutely clear).
258            The action now is always to scan all levels of directory, and just
259            apply the include/exclude patterns to regular files.
261    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
262        --exclude_dir in the tests to avoid scanning .svn directories.
264    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
265        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
266        doesn't support NULs in patterns.
268    7.  Added some missing "const"s to declarations of static tables in
269        pcre_compile.c and pcre_dfa_exec.c.
271    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
272        caused by fix #2  above. (Subsequently also a second patch to fix the
273        first patch. And a third patch - this was a messy problem.)
275    9.  Applied Craig's patch to remove the use of push_back().
277    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
278        matching function regexec().
280    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
281        which, however, unlike Perl's \g{...}, are subroutine calls, not back
282        references. PCRE supports relative numbers with this syntax (I don't think
283        Oniguruma does).
285    12. Previously, a group with a zero repeat such as (...){0} was completely
286        omitted from the compiled regex. However, this means that if the group
287        was called as a subroutine from elsewhere in the pattern, things went wrong
288        (an internal error was given). Such groups are now left in the compiled
289        pattern, with a new opcode that causes them to be skipped at execution
290        time.
292    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
293        to the way PCRE behaves:
295        (a) A lone ] character is dis-allowed (Perl treats it as data).
297        (b) A back reference to an unmatched subpattern matches an empty string
298            (Perl fails the current match path).
300        (c) A data ] in a character class must be notated as \] because if the
301            first data character in a class is ], it defines an empty class. (In
302            Perl it is not possible to have an empty class.) The empty class []
303            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
304            The negative empty class [^] matches any one character, independently
305            of the DOTALL setting.
307    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
308        non-existent subpattern following a character class starting with ']' and
309        containing () gave an internal compiling error instead of "reference to
310        non-existent subpattern". Fortunately, when the pattern did exist, the
311        compiled code was correct. (When scanning forwards to check for the
312        existencd of the subpattern, it was treating the data ']' as terminating
313        the class, so got the count wrong. When actually compiling, the reference
314        was subsequently set up correctly.)
316    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
317        it was being rejected as not supported by pcre_dfa_exec(), even though
318        other assertions are supported. I have made pcre_dfa_exec() support
319        (*FAIL).
321    16. The implementation of 13c above involved the invention of a new opcode,
322        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
323        cannot be changed at match time, I realized I could make a small
324        improvement to matching performance by compiling OP_ALLANY instead of
325        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
326        on the OP_ANY path.
328    17. Compiling pcretest on Windows with readline support failed without the
329        following two fixes: (1) Make the unistd.h include conditional on
330        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
332    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
333        ncurses library to be included for pcretest when ReadLine support is
334        requested, but also to allow for it to be overridden. This patch came from
335        Daniel Bergström.
337    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
338        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
339        any errors with the current Unicode tables. Thanks to Peter Kankowski for
340        spotting this.
343    Version 7.6 28-Jan-08
344    ---------------------
346    1.  A character class containing a very large number of characters with
347        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
348        overflow.
350    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
351        HAVE_LONG_LONG is not defined.
353    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
354        bring them up to date and include new features. This patch includes:
356        - Fixed PH's badly added libz and libbz2 support.
357        - Fixed a problem with static linking.
358        - Added pcredemo. [But later removed - see 7 below.]
359        - Fixed dftables problem and added an option.
360        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
361            HAVE_LONG_LONG.
362        - Added readline support for pcretest.
363        - Added an listing of the option settings after cmake has run.
365    4.  A user submitted a patch to Makefile that makes it easy to create
366        "pcre.dll" under mingw when using Configure/Make. I added stuff to
367        Makefile.am that cause it to include this special target, without
368        affecting anything else. Note that the same mingw target plus all
369        the other distribution libraries and programs are now supported
370        when configuring with CMake (see 6 below) instead of with
371        Configure/Make.
373    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
374        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
375        exported in the Windows port". It has not yet been confirmed that the patch
376        solves the problem, but it does no harm.
378    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
379        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
380        with CMake, and also correct the comment about stack recursion.
382    7.  Remove the automatic building of pcredemo from the ./configure system and
383        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
384        of a program that users should build themselves after PCRE is installed, so
385        building it automatically is not really right. What is more, it gave
386        trouble in some build environments.
388    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
391    Version 7.5 10-Jan-08
392  ---------------------  ---------------------
394  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 463  Version 7.5 12-Nov-07
463      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
464      non-matching lines.      non-matching lines.
466  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
468    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
469      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
470      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
471      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
473  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
474      inclusion of <windows.h> to before rather than after the definition of      inclusion of <windows.h> to before rather than after the definition of
475      INVALID_FILE_ATTRIBUTES (patch from David Byron).      INVALID_FILE_ATTRIBUTES (patch from David Byron).
477  16. Specifying a possessive quantifier with a specific limit for a Unicode  17. Specifying a possessive quantifier with a specific limit for a Unicode
478      character property caused pcre_compile() to compile bad code, which led at      character property caused pcre_compile() to compile bad code, which led at
479      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this      runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
480      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
481      caused the error; without that there was no problem.      caused the error; without that there was no problem.
483  17. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.  18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
485    19. Added --enable-pcretest-libreadline.
487    20. In pcrecpp.cc, the variable 'count' was incremented twice in
488        RE::GlobalReplace(). As a result, the number of replacements returned was
489        double what it should be. I removed one of the increments, but Craig sent a
490        later patch that removed the other one (the right fix) and added unit tests
491        that check the return values (which was not done before).
493    21. Several CMake things:
495        (1) Arranged that, when cmake is used on Unix, the libraries end up with
496            the names libpcre and libpcreposix, not just pcre and pcreposix.
498        (2) The above change means that pcretest and pcregrep are now correctly
499            linked with the newly-built libraries, not previously installed ones.
503    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
504        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
505        UTF-8 newline character). The key issue is that the pattern starts .*;
506        this means that the match must be either at the beginning, or after a
507        newline. The bug was in the code for advancing after a failed match and
508        checking that the new position followed a newline. It was not taking
509        account of UTF-8 characters correctly.
511    23. PCRE was behaving differently from Perl in the way it recognized POSIX
512        character classes. PCRE was not treating the sequence [:...:] as a
513        character class unless the ... were all letters. Perl, however, seems to
514        allow any characters between [: and :], though of course it rejects as
515        unknown any "names" that contain non-letters, because all the known class
516        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
517        for example, whereas PCRE did not - it did not recognize a POSIX character
518        class. This seemed a bit dangerous, so the code has been changed to be
519        closer to Perl. The behaviour is not identical to Perl, because PCRE will
520        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
521        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
522        Perl does, and where it didn't before.
524  18. Added --enable-pcretest-libreadline.  24. Rewrite so as to remove the single use of %n from pcregrep because in some
525        Windows environments %n is disabled by default.
528  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

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

  ViewVC Help
Powered by ViewVC 1.1.5