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

Diff of /code/trunk/ChangeLog

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

revision 332 by ph10, Sat Apr 5 16:11:05 2008 UTC revision 454 by ph10, Tue Sep 22 09:42:11 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.7 05-Mar-08  Version 8.00 ??-???-??
5    ----------------------
6    
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.
11    
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.
15    
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.
23    
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.
28    
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.
33    
34    6.  No libpcreposix.pc file was created for pkg-config; there was just
35        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
36    
37    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
38        when UCP support is not needed, by modifying the Python script that
39        generates it from Unicode data files. This should not matter if the module
40        is correctly used as a library, but I received one complaint about 50K of
41        unwanted data. My guess is that the person linked everything into his
42        program rather than using a library. Anyway, it does no harm.
43    
44    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
45        was a minimum greater than 1 for a wide character in a possessive
46        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
47        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
48        character. Chaos in the form of incorrect output or a compiling loop could
49        result.
50    
51    9.  The restrictions on what a pattern can contain when partial matching is
52        requested for pcre_exec() have been removed. All patterns can now be
53        partially matched by this function. In addition, if there are at least two
54        slots in the offset vector, the offset of the earliest inspected character
55        for the match and the offset of the end of the subject are set in them when
56        PCRE_ERROR_PARTIAL is returned.
57    
58    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
59        synonymous with PCRE_PARTIAL, for backwards compatibility, and
60        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
61        and may be more useful for multi-segment matching, especially with
62        pcre_exec().
63    
64    11. Partial matching with pcre_exec() is now more intuitive. A partial match
65        used to be given if ever the end of the subject was reached; now it is
66        given only if matching could not proceed because another character was
67        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
68        string "Z", which now yields "no match" instead of "partial match". In the
69        case of pcre_dfa_exec(), "no match" is given if every matching path for the
70        final character ended with (*FAIL).
71    
72    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
73        if the pattern had a "must contain" character that was already found in the
74        earlier partial match, unless partial matching was again requested. For
75        example, with the pattern /dog.(body)?/, the "must contain" character is
76        "g". If the first part-match was for the string "dog", restarting with
77        "sbody" failed. This bug has been fixed.
78    
79    13. The string returned by pcre_dfa_exec() after a partial match has been
80        changed so that it starts at the first inspected character rather than the
81        first character of the match. This makes a difference only if the pattern
82        starts with a lookbehind assertion or \b or \B (\K is not supported by
83        pcre_dfa_exec()). It's an incompatible change, but it makes the two
84        matching functions compatible, and I think it's the right thing to do.
85    
86    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
87        so that the demonstration program is easily available in environments where
88        PCRE has not been installed from source.
89    
90    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
91        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
92        library.
93    
94    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
95        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
96        is not the first non-POSIX option to be added. Clearly some people find
97        these options useful.
98    
99    17. If a caller to the POSIX matching function regexec() passes a non-zero
100        value for nmatch with a NULL value for pmatch, the value of
101        nmatch is forced to zero.
102    
103    18. RunGrepTest did not have a test for the availability of the -u option of
104        the diff command, as RunTest does. It now checks in the same way as
105        RunTest, and also checks for the -b option.
106    
107    19. If an odd number of negated classes containing just a single character
108        interposed, within parentheses, between a forward reference to a named
109        subpattern and the definition of the subpattern, compilation crashed with
110        an internal error, complaining that it could not find the referenced
111        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
112        [The bug was that it was starting one character too far in when skipping
113        over the character class, thus treating the ] as data rather than
114        terminating the class. This meant it could skip too much.]
115    
116    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
117        /g option in pcretest when the pattern contains \K, which makes it possible
118        to have an empty string match not at the start, even when the pattern is
119        anchored. Updated pcretest and pcredemo to use this option.
120    
121    21. If the maximum number of capturing subpatterns in a recursion was greater
122        than the maximum at the outer level, the higher number was returned, but
123        with unset values at the outer level. The correct (outer level) value is
124        now given.
125    
126    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
127        PCRE did not set those parentheses (unlike Perl). I have now found a way to
128        make it do so. The string so far is captured, making this feature
129        compatible with Perl.
130    
131    23. The tests have been re-organized, adding tests 11 and 12, to make it
132        possible to check the Perl 5.10 features against Perl 5.10.
133    
134    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
135        pattern matches a fixed length string. PCRE did not allow this; now it
136        does. Neither allows recursion.
137    
138    
139    Version 7.9 11-Apr-09
140    ---------------------
141    
142    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
143        (pcretest), all targets were linked against these libraries. This included
144        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
145        libraries. This caused unwanted dependencies to be created. This problem
146        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
147        pcretest is linked with readline.
148    
149    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
150        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
151        moved outside it again, because FALSE and TRUE are already defined in AIX,
152        but BOOL is not.
153    
154    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
155        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
156    
157    4.  The pcregrep documentation said spaces were inserted as well as colons (or
158        hyphens) following file names and line numbers when outputting matching
159        lines. This is not true; no spaces are inserted. I have also clarified the
160        wording for the --colour (or --color) option.
161    
162    5.  In pcregrep, when --colour was used with -o, the list of matching strings
163        was not coloured; this is different to GNU grep, so I have changed it to be
164        the same.
165    
166    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
167        each matching line was coloured. Now it goes on to look for further matches
168        of any of the test patterns, which is the same behaviour as GNU grep.
169    
170    7.  A pattern that could match an empty string could cause pcregrep to loop; it
171        doesn't make sense to accept an empty string match in pcregrep, so I have
172        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
173        seems to be how GNU grep behaves.
174    
175    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
176        start or after a newline", because the conditional assertion was not being
177        correctly handled. The rule now is that both the assertion and what follows
178        in the first alternative must satisfy the test.
179    
180    9.  If auto-callout was enabled in a pattern with a conditional group whose
181        condition was an assertion, PCRE could crash during matching, both with
182        pcre_exec() and pcre_dfa_exec().
183    
184    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
185        used for matching.
186    
187    11. Unicode property support in character classes was not working for
188        characters (bytes) greater than 127 when not in UTF-8 mode.
189    
190    12. Added the -M command line option to pcretest.
191    
192    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
193    
194    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
195    
196    16. Added comments and documentation about mis-use of no_arg in the C++
197        wrapper.
198    
199    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
200        from Martin Jerabek that uses macro names for all relevant character and
201        string constants.
202    
203    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
204        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
205        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
206        these, but not everybody uses configure.
207    
208    19. A conditional group that had only one branch was not being correctly
209        recognized as an item that could match an empty string. This meant that an
210        enclosing group might also not be so recognized, causing infinite looping
211        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
212        with the subject "ab", where knowledge that the repeated group can match
213        nothing is needed in order to break the loop.
214    
215    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
216        exec(), but without supplying a callout function, matching went wrong.
217    
218    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
219        leak if the size of the offset vector was greater than 30. When the vector
220        is smaller, the saved offsets during recursion go onto a local stack
221        vector, but for larger vectors malloc() is used. It was failing to free
222        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
223        error, in fact).
224    
225    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
226        heapframe that is used only when UTF-8 support is enabled. This caused no
227        problem, but was untidy.
228    
229    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
230        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
231        included within another project.
232    
233    24. Steven Van Ingelgem's patches to add more options to the CMake support,
234        slightly modified by me:
235    
236          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
237              not building pcregrep.
238    
239          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
240              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
241    
242    25. Forward references, both numeric and by name, in patterns that made use of
243        duplicate group numbers, could behave incorrectly or give incorrect errors,
244        because when scanning forward to find the reference group, PCRE was not
245        taking into account the duplicate group numbers. A pattern such as
246        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
247    
248    26. Changed a few more instances of "const unsigned char *" to USPTR, making
249        the feature of a custom pointer more persuasive (as requested by a user).
250    
251    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
252        pcretest.c, inside #ifndefs, because it seems they are sometimes already
253        pre-defined.
254    
255    28. Added support for (*UTF8) at the start of a pattern.
256    
257    29. Arrange for flags added by the "release type" setting in CMake to be shown
258        in the configuration summary.
259    
260    
261    Version 7.8 05-Sep-08
262    ---------------------
263    
264    1.  Replaced UCP searching code with optimized version as implemented for Ad
265        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
266        stage table and inline lookup instead of a function, giving speed ups of 2
267        to 5 times on some simple patterns that I tested. Permission was given to
268        distribute the MultiStage2.py script that generates the tables (it's not in
269        the tarball, but is in the Subversion repository).
270    
271    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
272        scripts.
273    
274    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
275        a group with a zero qualifier. The result of the study could be incorrect,
276        or the function might crash, depending on the pattern.
277    
278    4.  Caseless matching was not working for non-ASCII characters in back
279        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
280        It now works when Unicode Property Support is available.
281    
282    5.  In pcretest, an escape such as \x{de} in the data was always generating
283        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
284        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
285        truncation.
286    
287    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
288    
289    7.  Added two (int) casts to pcregrep when printing the difference of two
290        pointers, in case they are 64-bit values.
291    
292    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
293        test 2 if it fails.
294    
295    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
296        and a #define of that name to empty if it is not externally set. This is to
297        allow users of MSVC to set it if necessary.
298    
299    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
300        the convenience functions in the pcre_get.c source file.
301    
302    11. An option change at the start of a pattern that had top-level alternatives
303        could cause overwriting and/or a crash. This command provoked a crash in
304        some environments:
305    
306          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
307    
308        This potential security problem was recorded as CVE-2008-2371.
309    
310    12. For a pattern where the match had to start at the beginning or immediately
311        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
312        pcre_dfa_exec() could read past the end of the passed subject if there was
313        no match. To help with detecting such bugs (e.g. with valgrind), I modified
314        pcretest so that it places the subject at the end of its malloc-ed buffer.
315    
316    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
317        exec() might read past the end of the data buffer in UTF-8 mode.
318    
319    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
320        the data contained the byte 0x85 as part of a UTF-8 character within its
321        first line. This applied both to normal and DFA matching.
322    
323    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
324        /^[^d]*?$/8 failed to match "abc".
325    
326    16. Added a missing copyright notice to pcrecpp_internal.h.
327    
328    17. Make it more clear in the documentation that values returned from
329        pcre_exec() in ovector are byte offsets, not character counts.
330    
331    18. Tidied a few places to stop certain compilers from issuing warnings.
332    
333    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
334        supplied by Stefan Weber. I made a further small update for 7.8 because
335        there is a change of source arrangements: the pcre_searchfuncs.c module is
336        replaced by pcre_ucd.c.
337    
338    
339    Version 7.7 07-May-08
340  ---------------------  ---------------------
341    
342  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert  1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
343      a string to a long long, pretend we don't even have a long long." This is      a string to a long long, pretend we don't even have a long long." This is
344      done by checking for the strtoq, strtoll, and _strtoi64 functions.      done by checking for the strtoq, strtoll, and _strtoi64 functions.
345    
346  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with  2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
347      pre-7.6 versions, which defined a global no_arg variable instead of putting      pre-7.6 versions, which defined a global no_arg variable instead of putting
348      it in the RE class. (See also #8 below.)      it in the RE class. (See also #8 below.)
349    
350  3.  Remove a line of dead code, identified by coverity and reported by Nuno  3.  Remove a line of dead code, identified by coverity and reported by Nuno
351      Lopes.      Lopes.
352    
353  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:  4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
354    
355      (1) The include/exclude patterns were being applied to the whole pathnames      (1) The include/exclude patterns were being applied to the whole pathnames
356          of files, instead of just to the final components.          of files, instead of just to the final components.
357    
358      (2) If there was more than one level of directory, the subdirectories were      (2) If there was more than one level of directory, the subdirectories were
359          skipped unless they satisfied the include/exclude conditions. This is          skipped unless they satisfied the include/exclude conditions. This is
360          inconsistent with GNU grep (and could even be seen as contrary to the          inconsistent with GNU grep (and could even be seen as contrary to the
361          pcregrep specification - which I improved to make it absolutely clear).          pcregrep specification - which I improved to make it absolutely clear).
362          The action now is always to scan all levels of directory, and just          The action now is always to scan all levels of directory, and just
363          apply the include/exclude patterns to regular files.          apply the include/exclude patterns to regular files.
364    
365  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used  5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
366      --exclude_dir in the tests to avoid scanning .svn directories.      --exclude_dir in the tests to avoid scanning .svn directories.
367    
368  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the  6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
369      NUL character as backslash + 0 rather than backslash + NUL, because PCRE      NUL character as backslash + 0 rather than backslash + NUL, because PCRE
370      doesn't support NULs in patterns.      doesn't support NULs in patterns.
371    
372  7.  Added some missing "const"s to declarations of static tables in  7.  Added some missing "const"s to declarations of static tables in
373      pcre_compile.c and pcre_dfa_exec.c.      pcre_compile.c and pcre_dfa_exec.c.
374    
375  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was  8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
376      caused by fix #2  above. (Subsequently also a second patch to fix the      caused by fix #2  above. (Subsequently also a second patch to fix the
377      first patch. And a third patch - this was a messy problem.)      first patch. And a third patch - this was a messy problem.)
378    
379  9.  Applied Craig's patch to remove the use of push_back().  9.  Applied Craig's patch to remove the use of push_back().
380    
381  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX  10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
382      matching function regexec().      matching function regexec().
383    
384    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
385        which, however, unlike Perl's \g{...}, are subroutine calls, not back
386        references. PCRE supports relative numbers with this syntax (I don't think
387        Oniguruma does).
388    
389    12. Previously, a group with a zero repeat such as (...){0} was completely
390        omitted from the compiled regex. However, this means that if the group
391        was called as a subroutine from elsewhere in the pattern, things went wrong
392        (an internal error was given). Such groups are now left in the compiled
393        pattern, with a new opcode that causes them to be skipped at execution
394        time.
395    
396    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
397        to the way PCRE behaves:
398    
399        (a) A lone ] character is dis-allowed (Perl treats it as data).
400    
401        (b) A back reference to an unmatched subpattern matches an empty string
402            (Perl fails the current match path).
403    
404        (c) A data ] in a character class must be notated as \] because if the
405            first data character in a class is ], it defines an empty class. (In
406            Perl it is not possible to have an empty class.) The empty class []
407            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
408            The negative empty class [^] matches any one character, independently
409            of the DOTALL setting.
410    
411    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
412        non-existent subpattern following a character class starting with ']' and
413        containing () gave an internal compiling error instead of "reference to
414        non-existent subpattern". Fortunately, when the pattern did exist, the
415        compiled code was correct. (When scanning forwards to check for the
416        existencd of the subpattern, it was treating the data ']' as terminating
417        the class, so got the count wrong. When actually compiling, the reference
418        was subsequently set up correctly.)
419    
420    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
421        it was being rejected as not supported by pcre_dfa_exec(), even though
422        other assertions are supported. I have made pcre_dfa_exec() support
423        (*FAIL).
424    
425    16. The implementation of 13c above involved the invention of a new opcode,
426        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
427        cannot be changed at match time, I realized I could make a small
428        improvement to matching performance by compiling OP_ALLANY instead of
429        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
430        on the OP_ANY path.
431    
432    17. Compiling pcretest on Windows with readline support failed without the
433        following two fixes: (1) Make the unistd.h include conditional on
434        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
435    
436    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
437        ncurses library to be included for pcretest when ReadLine support is
438        requested, but also to allow for it to be overridden. This patch came from
439        Daniel Bergström.
440    
441    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
442        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
443        any errors with the current Unicode tables. Thanks to Peter Kankowski for
444        spotting this.
445    
446    
447  Version 7.6 28-Jan-08  Version 7.6 28-Jan-08
448  ---------------------  ---------------------

Legend:
Removed from v.332  
changed lines
  Added in v.454

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12