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

Legend:
Removed from v.287  
changed lines
  Added in v.412

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12