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

Diff of /code/trunk/ChangeLog

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

revision 216 by ph10, Wed Aug 15 14:35:57 2007 UTC revision 472 by ph10, Fri Dec 11 16:42:50 2009 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
3    
4  Version 7.3 09-Aug-07  Version 8.01 11-Dec-09
5    ----------------------
6    
7    1.  If a pattern contained a conditional subpattern with only one branch (in
8        particular, this includes all (DEFINE) patterns), a call to pcre_study()
9        computed the wrong minimum data length (which is of course zero for such
10        subpatterns).
11    
12    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
13        the pattern is reset in the first branch, pcre_compile() failed with
14        "internal error: code overflow at offset...". This happened only when
15        the reset was to the original external option setting. (An optimization
16        abstracts leading options settings into an external setting, which was the
17        cause of this.)
18    
19    
20    Version 8.00 19-Oct-09
21    ----------------------
22    
23    1.  The table for translating pcre_compile() error codes into POSIX error codes
24        was out-of-date, and there was no check on the pcre_compile() error code
25        being within the table. This could lead to an OK return being given in
26        error.
27    
28    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
29        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
30        in a Windows environment.
31    
32    3.  The pcregrep --count option prints the count for each file even when it is
33        zero, as does GNU grep. However, pcregrep was also printing all files when
34        --files-with-matches was added. Now, when both options are given, it prints
35        counts only for those files that have at least one match. (GNU grep just
36        prints the file name in this circumstance, but including the count seems
37        more useful - otherwise, why use --count?) Also ensured that the
38        combination -clh just lists non-zero counts, with no names.
39    
40    4.  The long form of the pcregrep -F option was incorrectly implemented as
41        --fixed_strings instead of --fixed-strings. This is an incompatible change,
42        but it seems right to fix it, and I didn't think it was worth preserving
43        the old behaviour.
44    
45    5.  The command line items --regex=pattern and --regexp=pattern were not
46        recognized by pcregrep, which required --regex pattern or --regexp pattern
47        (with a space rather than an '='). The man page documented the '=' forms,
48        which are compatible with GNU grep; these now work.
49    
50    6.  No libpcreposix.pc file was created for pkg-config; there was just
51        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
52    
53    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
54        when UCP support is not needed, by modifying the Python script that
55        generates it from Unicode data files. This should not matter if the module
56        is correctly used as a library, but I received one complaint about 50K of
57        unwanted data. My guess is that the person linked everything into his
58        program rather than using a library. Anyway, it does no harm.
59    
60    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
61        was a minimum greater than 1 for a wide character in a possessive
62        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
63        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
64        character. Chaos in the form of incorrect output or a compiling loop could
65        result.
66    
67    9.  The restrictions on what a pattern can contain when partial matching is
68        requested for pcre_exec() have been removed. All patterns can now be
69        partially matched by this function. In addition, if there are at least two
70        slots in the offset vector, the offset of the earliest inspected character
71        for the match and the offset of the end of the subject are set in them when
72        PCRE_ERROR_PARTIAL is returned.
73    
74    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
75        synonymous with PCRE_PARTIAL, for backwards compatibility, and
76        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
77        and may be more useful for multi-segment matching.
78    
79    11. Partial matching with pcre_exec() is now more intuitive. A partial match
80        used to be given if ever the end of the subject was reached; now it is
81        given only if matching could not proceed because another character was
82        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
83        string "Z", which now yields "no match" instead of "partial match". In the
84        case of pcre_dfa_exec(), "no match" is given if every matching path for the
85        final character ended with (*FAIL).
86    
87    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
88        if the pattern had a "must contain" character that was already found in the
89        earlier partial match, unless partial matching was again requested. For
90        example, with the pattern /dog.(body)?/, the "must contain" character is
91        "g". If the first part-match was for the string "dog", restarting with
92        "sbody" failed. This bug has been fixed.
93    
94    13. The string returned by pcre_dfa_exec() after a partial match has been
95        changed so that it starts at the first inspected character rather than the
96        first character of the match. This makes a difference only if the pattern
97        starts with a lookbehind assertion or \b or \B (\K is not supported by
98        pcre_dfa_exec()). It's an incompatible change, but it makes the two
99        matching functions compatible, and I think it's the right thing to do.
100    
101    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
102        so that the demonstration program is easily available in environments where
103        PCRE has not been installed from source.
104    
105    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
106        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
107        library.
108    
109    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
110        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
111        is not the first non-POSIX option to be added. Clearly some people find
112        these options useful.
113    
114    17. If a caller to the POSIX matching function regexec() passes a non-zero
115        value for nmatch with a NULL value for pmatch, the value of
116        nmatch is forced to zero.
117    
118    18. RunGrepTest did not have a test for the availability of the -u option of
119        the diff command, as RunTest does. It now checks in the same way as
120        RunTest, and also checks for the -b option.
121    
122    19. If an odd number of negated classes containing just a single character
123        interposed, within parentheses, between a forward reference to a named
124        subpattern and the definition of the subpattern, compilation crashed with
125        an internal error, complaining that it could not find the referenced
126        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
127        [The bug was that it was starting one character too far in when skipping
128        over the character class, thus treating the ] as data rather than
129        terminating the class. This meant it could skip too much.]
130    
131    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
132        /g option in pcretest when the pattern contains \K, which makes it possible
133        to have an empty string match not at the start, even when the pattern is
134        anchored. Updated pcretest and pcredemo to use this option.
135    
136    21. If the maximum number of capturing subpatterns in a recursion was greater
137        than the maximum at the outer level, the higher number was returned, but
138        with unset values at the outer level. The correct (outer level) value is
139        now given.
140    
141    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
142        PCRE did not set those parentheses (unlike Perl). I have now found a way to
143        make it do so. The string so far is captured, making this feature
144        compatible with Perl.
145    
146    23. The tests have been re-organized, adding tests 11 and 12, to make it
147        possible to check the Perl 5.10 features against Perl 5.10.
148    
149    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
150        pattern matches a fixed length string. PCRE did not allow this; now it
151        does. Neither allows recursion.
152    
153    25. I finally figured out how to implement a request to provide the minimum
154        length of subject string that was needed in order to match a given pattern.
155        (It was back references and recursion that I had previously got hung up
156        on.) This code has now been added to pcre_study(); it finds a lower bound
157        to the length of subject needed. It is not necessarily the greatest lower
158        bound, but using it to avoid searching strings that are too short does give
159        some useful speed-ups. The value is available to calling programs via
160        pcre_fullinfo().
161    
162    26. While implementing 25, I discovered to my embarrassment that pcretest had
163        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
164        study optimizations had never been tested with that matching function.
165        Oops. What is worse, even when it was passed study data, there was a bug in
166        pcre_dfa_exec() that meant it never actually used it. Double oops. There
167        were also very few tests of studied patterns with pcre_dfa_exec().
168    
169    27. If (?| is used to create subpatterns with duplicate numbers, they are now
170        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
171        on the other side of the coin, they are no longer allowed to have different
172        names, because these cannot be distinguished in PCRE, and this has caused
173        confusion. (This is a difference from Perl.)
174    
175    28. When duplicate subpattern names are present (necessarily with different
176        numbers, as required by 27 above), and a test is made by name in a
177        conditional pattern, either for a subpattern having been matched, or for
178        recursion in such a pattern, all the associated numbered subpatterns are
179        tested, and the overall condition is true if the condition is true for any
180        one of them. This is the way Perl works, and is also more like the way
181        testing by number works.
182    
183    
184    Version 7.9 11-Apr-09
185    ---------------------
186    
187    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
188        (pcretest), all targets were linked against these libraries. This included
189        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
190        libraries. This caused unwanted dependencies to be created. This problem
191        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
192        pcretest is linked with readline.
193    
194    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
195        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
196        moved outside it again, because FALSE and TRUE are already defined in AIX,
197        but BOOL is not.
198    
199    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
200        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
201    
202    4.  The pcregrep documentation said spaces were inserted as well as colons (or
203        hyphens) following file names and line numbers when outputting matching
204        lines. This is not true; no spaces are inserted. I have also clarified the
205        wording for the --colour (or --color) option.
206    
207    5.  In pcregrep, when --colour was used with -o, the list of matching strings
208        was not coloured; this is different to GNU grep, so I have changed it to be
209        the same.
210    
211    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
212        each matching line was coloured. Now it goes on to look for further matches
213        of any of the test patterns, which is the same behaviour as GNU grep.
214    
215    7.  A pattern that could match an empty string could cause pcregrep to loop; it
216        doesn't make sense to accept an empty string match in pcregrep, so I have
217        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
218        seems to be how GNU grep behaves.
219    
220    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
221        start or after a newline", because the conditional assertion was not being
222        correctly handled. The rule now is that both the assertion and what follows
223        in the first alternative must satisfy the test.
224    
225    9.  If auto-callout was enabled in a pattern with a conditional group whose
226        condition was an assertion, PCRE could crash during matching, both with
227        pcre_exec() and pcre_dfa_exec().
228    
229    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
230        used for matching.
231    
232    11. Unicode property support in character classes was not working for
233        characters (bytes) greater than 127 when not in UTF-8 mode.
234    
235    12. Added the -M command line option to pcretest.
236    
237    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
238    
239    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
240    
241    16. Added comments and documentation about mis-use of no_arg in the C++
242        wrapper.
243    
244    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
245        from Martin Jerabek that uses macro names for all relevant character and
246        string constants.
247    
248    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
249        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
250        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
251        these, but not everybody uses configure.
252    
253    19. A conditional group that had only one branch was not being correctly
254        recognized as an item that could match an empty string. This meant that an
255        enclosing group might also not be so recognized, causing infinite looping
256        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
257        with the subject "ab", where knowledge that the repeated group can match
258        nothing is needed in order to break the loop.
259    
260    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
261        exec(), but without supplying a callout function, matching went wrong.
262    
263    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
264        leak if the size of the offset vector was greater than 30. When the vector
265        is smaller, the saved offsets during recursion go onto a local stack
266        vector, but for larger vectors malloc() is used. It was failing to free
267        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
268        error, in fact).
269    
270    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
271        heapframe that is used only when UTF-8 support is enabled. This caused no
272        problem, but was untidy.
273    
274    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
275        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
276        included within another project.
277    
278    24. Steven Van Ingelgem's patches to add more options to the CMake support,
279        slightly modified by me:
280    
281          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
282              not building pcregrep.
283    
284          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
285              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
286    
287    25. Forward references, both numeric and by name, in patterns that made use of
288        duplicate group numbers, could behave incorrectly or give incorrect errors,
289        because when scanning forward to find the reference group, PCRE was not
290        taking into account the duplicate group numbers. A pattern such as
291        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
292    
293    26. Changed a few more instances of "const unsigned char *" to USPTR, making
294        the feature of a custom pointer more persuasive (as requested by a user).
295    
296    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
297        pcretest.c, inside #ifndefs, because it seems they are sometimes already
298        pre-defined.
299    
300    28. Added support for (*UTF8) at the start of a pattern.
301    
302    29. Arrange for flags added by the "release type" setting in CMake to be shown
303        in the configuration summary.
304    
305    
306    Version 7.8 05-Sep-08
307    ---------------------
308    
309    1.  Replaced UCP searching code with optimized version as implemented for Ad
310        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
311        stage table and inline lookup instead of a function, giving speed ups of 2
312        to 5 times on some simple patterns that I tested. Permission was given to
313        distribute the MultiStage2.py script that generates the tables (it's not in
314        the tarball, but is in the Subversion repository).
315    
316    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
317        scripts.
318    
319    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
320        a group with a zero qualifier. The result of the study could be incorrect,
321        or the function might crash, depending on the pattern.
322    
323    4.  Caseless matching was not working for non-ASCII characters in back
324        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
325        It now works when Unicode Property Support is available.
326    
327    5.  In pcretest, an escape such as \x{de} in the data was always generating
328        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
329        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
330        truncation.
331    
332    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
333    
334    7.  Added two (int) casts to pcregrep when printing the difference of two
335        pointers, in case they are 64-bit values.
336    
337    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
338        test 2 if it fails.
339    
340    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
341        and a #define of that name to empty if it is not externally set. This is to
342        allow users of MSVC to set it if necessary.
343    
344    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
345        the convenience functions in the pcre_get.c source file.
346    
347    11. An option change at the start of a pattern that had top-level alternatives
348        could cause overwriting and/or a crash. This command provoked a crash in
349        some environments:
350    
351          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
352    
353        This potential security problem was recorded as CVE-2008-2371.
354    
355    12. For a pattern where the match had to start at the beginning or immediately
356        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
357        pcre_dfa_exec() could read past the end of the passed subject if there was
358        no match. To help with detecting such bugs (e.g. with valgrind), I modified
359        pcretest so that it places the subject at the end of its malloc-ed buffer.
360    
361    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
362        exec() might read past the end of the data buffer in UTF-8 mode.
363    
364    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
365        the data contained the byte 0x85 as part of a UTF-8 character within its
366        first line. This applied both to normal and DFA matching.
367    
368    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
369        /^[^d]*?$/8 failed to match "abc".
370    
371    16. Added a missing copyright notice to pcrecpp_internal.h.
372    
373    17. Make it more clear in the documentation that values returned from
374        pcre_exec() in ovector are byte offsets, not character counts.
375    
376    18. Tidied a few places to stop certain compilers from issuing warnings.
377    
378    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
379        supplied by Stefan Weber. I made a further small update for 7.8 because
380        there is a change of source arrangements: the pcre_searchfuncs.c module is
381        replaced by pcre_ucd.c.
382    
383    
384    Version 7.7 07-May-08
385    ---------------------
386    
387    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
388        a string to a long long, pretend we don't even have a long long." This is
389        done by checking for the strtoq, strtoll, and _strtoi64 functions.
390    
391    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
392        pre-7.6 versions, which defined a global no_arg variable instead of putting
393        it in the RE class. (See also #8 below.)
394    
395    3.  Remove a line of dead code, identified by coverity and reported by Nuno
396        Lopes.
397    
398    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
399    
400        (1) The include/exclude patterns were being applied to the whole pathnames
401            of files, instead of just to the final components.
402    
403        (2) If there was more than one level of directory, the subdirectories were
404            skipped unless they satisfied the include/exclude conditions. This is
405            inconsistent with GNU grep (and could even be seen as contrary to the
406            pcregrep specification - which I improved to make it absolutely clear).
407            The action now is always to scan all levels of directory, and just
408            apply the include/exclude patterns to regular files.
409    
410    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
411        --exclude_dir in the tests to avoid scanning .svn directories.
412    
413    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
414        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
415        doesn't support NULs in patterns.
416    
417    7.  Added some missing "const"s to declarations of static tables in
418        pcre_compile.c and pcre_dfa_exec.c.
419    
420    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
421        caused by fix #2  above. (Subsequently also a second patch to fix the
422        first patch. And a third patch - this was a messy problem.)
423    
424    9.  Applied Craig's patch to remove the use of push_back().
425    
426    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
427        matching function regexec().
428    
429    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
430        which, however, unlike Perl's \g{...}, are subroutine calls, not back
431        references. PCRE supports relative numbers with this syntax (I don't think
432        Oniguruma does).
433    
434    12. Previously, a group with a zero repeat such as (...){0} was completely
435        omitted from the compiled regex. However, this means that if the group
436        was called as a subroutine from elsewhere in the pattern, things went wrong
437        (an internal error was given). Such groups are now left in the compiled
438        pattern, with a new opcode that causes them to be skipped at execution
439        time.
440    
441    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
442        to the way PCRE behaves:
443    
444        (a) A lone ] character is dis-allowed (Perl treats it as data).
445    
446        (b) A back reference to an unmatched subpattern matches an empty string
447            (Perl fails the current match path).
448    
449        (c) A data ] in a character class must be notated as \] because if the
450            first data character in a class is ], it defines an empty class. (In
451            Perl it is not possible to have an empty class.) The empty class []
452            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
453            The negative empty class [^] matches any one character, independently
454            of the DOTALL setting.
455    
456    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
457        non-existent subpattern following a character class starting with ']' and
458        containing () gave an internal compiling error instead of "reference to
459        non-existent subpattern". Fortunately, when the pattern did exist, the
460        compiled code was correct. (When scanning forwards to check for the
461        existencd of the subpattern, it was treating the data ']' as terminating
462        the class, so got the count wrong. When actually compiling, the reference
463        was subsequently set up correctly.)
464    
465    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
466        it was being rejected as not supported by pcre_dfa_exec(), even though
467        other assertions are supported. I have made pcre_dfa_exec() support
468        (*FAIL).
469    
470    16. The implementation of 13c above involved the invention of a new opcode,
471        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
472        cannot be changed at match time, I realized I could make a small
473        improvement to matching performance by compiling OP_ALLANY instead of
474        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
475        on the OP_ANY path.
476    
477    17. Compiling pcretest on Windows with readline support failed without the
478        following two fixes: (1) Make the unistd.h include conditional on
479        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
480    
481    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
482        ncurses library to be included for pcretest when ReadLine support is
483        requested, but also to allow for it to be overridden. This patch came from
484        Daniel Bergström.
485    
486    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
487        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
488        any errors with the current Unicode tables. Thanks to Peter Kankowski for
489        spotting this.
490    
491    
492    Version 7.6 28-Jan-08
493    ---------------------
494    
495    1.  A character class containing a very large number of characters with
496        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
497        overflow.
498    
499    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
500        HAVE_LONG_LONG is not defined.
501    
502    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
503        bring them up to date and include new features. This patch includes:
504    
505        - Fixed PH's badly added libz and libbz2 support.
506        - Fixed a problem with static linking.
507        - Added pcredemo. [But later removed - see 7 below.]
508        - Fixed dftables problem and added an option.
509        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
510            HAVE_LONG_LONG.
511        - Added readline support for pcretest.
512        - Added an listing of the option settings after cmake has run.
513    
514    4.  A user submitted a patch to Makefile that makes it easy to create
515        "pcre.dll" under mingw when using Configure/Make. I added stuff to
516        Makefile.am that cause it to include this special target, without
517        affecting anything else. Note that the same mingw target plus all
518        the other distribution libraries and programs are now supported
519        when configuring with CMake (see 6 below) instead of with
520        Configure/Make.
521    
522    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
523        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
524        exported in the Windows port". It has not yet been confirmed that the patch
525        solves the problem, but it does no harm.
526    
527    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
528        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
529        with CMake, and also correct the comment about stack recursion.
530    
531    7.  Remove the automatic building of pcredemo from the ./configure system and
532        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
533        of a program that users should build themselves after PCRE is installed, so
534        building it automatically is not really right. What is more, it gave
535        trouble in some build environments.
536    
537    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
538    
539    
540    Version 7.5 10-Jan-08
541    ---------------------
542    
543    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
544        values in parens when parsing an RE using the C++ wrapper."
545    
546    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
547        Characters greater than 255 were excluded from the class instead of being
548        included.
549    
550    3.  The same bug as (2) above applied to negated POSIX classes such as
551        [:^space:].
552    
553    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
554        defined or documented. It seems to have been a typo for PCRE_STATIC, so
555        I have changed it.
556    
557    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
558        first named subpattern) and a construct such as (?&a) would reference the
559        first named subpattern whose name started with "a" (in other words, the
560        length check was missing). Both these problems are fixed. "Subpattern name
561        expected" is now given for (?&) (a zero-length name), and this patch also
562        makes it give the same error for \k'' (previously it complained that that
563        was a reference to a non-existent subpattern).
564    
565    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
566        this is right because (?- can be followed by option settings as well as by
567        digits. I have, however, made the messages clearer.
568    
569    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
570        than the number used in the conditional) now cause a compile-time error.
571        This is actually not compatible with Perl, which accepts such patterns, but
572        treats the conditional as always being FALSE (as PCRE used to), but it
573        seems to me that giving a diagnostic is better.
574    
575    8.  Change "alphameric" to the more common word "alphanumeric" in comments
576        and messages.
577    
578    9.  Fix two occurrences of "backslash" in comments that should have been
579        "backspace".
580    
581    10. Remove two redundant lines of code that can never be obeyed (their function
582        was moved elsewhere).
583    
584    11. The program that makes PCRE's Unicode character property table had a bug
585        which caused it to generate incorrect table entries for sequences of
586        characters that have the same character type, but are in different scripts.
587        It amalgamated them into a single range, with the script of the first of
588        them. In other words, some characters were in the wrong script. There were
589        thirteen such cases, affecting characters in the following ranges:
590    
591          U+002b0 - U+002c1
592          U+0060c - U+0060d
593          U+0061e - U+00612
594          U+0064b - U+0065e
595          U+0074d - U+0076d
596          U+01800 - U+01805
597          U+01d00 - U+01d77
598          U+01d9b - U+01dbf
599          U+0200b - U+0200f
600          U+030fc - U+030fe
601          U+03260 - U+0327f
602          U+0fb46 - U+0fbb1
603          U+10450 - U+1049d
604    
605    12. The -o option (show only the matching part of a line) for pcregrep was not
606        compatible with GNU grep in that, if there was more than one match in a
607        line, it showed only the first of them. It now behaves in the same way as
608        GNU grep.
609    
610    13. If the -o and -v options were combined for pcregrep, it printed a blank
611        line for every non-matching line. GNU grep prints nothing, and pcregrep now
612        does the same. The return code can be used to tell if there were any
613        non-matching lines.
614    
615    14. Added --file-offsets and --line-offsets to pcregrep.
616    
617    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
618        infinitely looping recursion. The bug was that positive lookaheads were not
619        being skipped when checking for a possible empty match (negative lookaheads
620        and both kinds of lookbehind were skipped).
621    
622    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
623        inclusion of <windows.h> to before rather than after the definition of
624        INVALID_FILE_ATTRIBUTES (patch from David Byron).
625    
626    17. Specifying a possessive quantifier with a specific limit for a Unicode
627        character property caused pcre_compile() to compile bad code, which led at
628        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
629        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
630        caused the error; without that there was no problem.
631    
632    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
633    
634    19. Added --enable-pcretest-libreadline.
635    
636    20. In pcrecpp.cc, the variable 'count' was incremented twice in
637        RE::GlobalReplace(). As a result, the number of replacements returned was
638        double what it should be. I removed one of the increments, but Craig sent a
639        later patch that removed the other one (the right fix) and added unit tests
640        that check the return values (which was not done before).
641    
642    21. Several CMake things:
643    
644        (1) Arranged that, when cmake is used on Unix, the libraries end up with
645            the names libpcre and libpcreposix, not just pcre and pcreposix.
646    
647        (2) The above change means that pcretest and pcregrep are now correctly
648            linked with the newly-built libraries, not previously installed ones.
649    
650        (3) Added PCRE_SUPPORT_LIBREADLINE, PCRE_SUPPORT_LIBZ, PCRE_SUPPORT_LIBBZ2.
651    
652    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
653        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
654        UTF-8 newline character). The key issue is that the pattern starts .*;
655        this means that the match must be either at the beginning, or after a
656        newline. The bug was in the code for advancing after a failed match and
657        checking that the new position followed a newline. It was not taking
658        account of UTF-8 characters correctly.
659    
660    23. PCRE was behaving differently from Perl in the way it recognized POSIX
661        character classes. PCRE was not treating the sequence [:...:] as a
662        character class unless the ... were all letters. Perl, however, seems to
663        allow any characters between [: and :], though of course it rejects as
664        unknown any "names" that contain non-letters, because all the known class
665        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
666        for example, whereas PCRE did not - it did not recognize a POSIX character
667        class. This seemed a bit dangerous, so the code has been changed to be
668        closer to Perl. The behaviour is not identical to Perl, because PCRE will
669        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
670        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
671        Perl does, and where it didn't before.
672    
673    24. Rewrite so as to remove the single use of %n from pcregrep because in some
674        Windows environments %n is disabled by default.
675    
676    
677    Version 7.4 21-Sep-07
678    ---------------------
679    
680    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
681        means that a class such as [\s] counted as "explicit reference to CR or
682        LF". That isn't really right - the whole point of the change was to try to
683        help when there was an actual mention of one of the two characters. So now
684        the change happens only if \r or \n (or a literal CR or LF) character is
685        encountered.
686    
687    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
688        of both had grown to the point where there were only 3 bits left.
689        Fortunately, there was spare space in the data structure, and so I have
690        moved the internal flags into a new 16-bit field to free up more option
691        bits.
692    
693    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
694        but did not set the internal JCHANGED flag - either of these is enough to
695        control the way the "get" function works - but the PCRE_INFO_JCHANGED
696        facility is supposed to tell if (?J) was ever used, so now (?J) at the
697        start sets both bits.
698    
699    4.  Added options (at build time, compile time, exec time) to change \R from
700        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
701    
702    5.  doc/pcresyntax.html was missing from the distribution.
703    
704    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
705        compatibility, even though it is no longer used.
706    
707    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
708        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
709        windows.h file is present (where different names are used). [This was
710        reversed later after testing - see 16 below.]
711    
712    8.  Changed all #include <config.h> to #include "config.h". There were also
713        some further <pcre.h> cases that I changed to "pcre.h".
714    
715    9.  When pcregrep was used with the --colour option, it missed the line ending
716        sequence off the lines that it output.
717    
718    10. It was pointed out to me that arrays of string pointers cause lots of
719        relocations when a shared library is dynamically loaded. A technique of
720        using a single long string with a table of offsets can drastically reduce
721        these. I have refactored PCRE in four places to do this. The result is
722        dramatic:
723    
724          Originally:                          290
725          After changing UCP table:            187
726          After changing error message table:   43
727          After changing table of "verbs"       36
728          After changing table of Posix names   22
729    
730        Thanks to the folks working on Gregex for glib for this insight.
731    
732    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
733        unicode-properties was also set.
734    
735    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
736    
737    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
738        checked only for CRLF.
739    
740    14. Added casts to pcretest.c to avoid compiler warnings.
741    
742    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
743    
744    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
745        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
746        entirely. This removes changes made in 7 above.
747    
748    17. The CMake files have been updated, and there is now more information about
749        building with CMake in the NON-UNIX-USE document.
750    
751    
752    Version 7.3 28-Aug-07
753  ---------------------  ---------------------
754    
755   1. In the rejigging of the build system that eventually resulted in 7.1, the   1. In the rejigging of the build system that eventually resulted in 7.1, the
# Line 98  Version 7.3 09-Aug-07 Line 846  Version 7.3 09-Aug-07
846      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the      the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
847      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still      full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
848      does: it's just the validity check that is more restrictive.      does: it's just the validity check that is more restrictive.
849    
850  16. Inserted checks for integer overflows during escape sequence (backslash)  16. Inserted checks for integer overflows during escape sequence (backslash)
851      processing, and also fixed erroneous offset values for syntax errors during      processing, and also fixed erroneous offset values for syntax errors during
852      backslash processing.      backslash processing.
853    
854  17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)  17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
855      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".      for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
856    
857  18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"  18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
858      caused an overrun.      caused an overrun.
859    
860  19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with  19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
861      something other than just ASCII characters) inside a group that had an      something other than just ASCII characters) inside a group that had an
862      unlimited repeat caused a loop at compile time (while checking to see      unlimited repeat caused a loop at compile time (while checking to see
863      whether the group could match an empty string).      whether the group could match an empty string).
864    
865    20. Debugging a pattern containing \p or \P could cause a crash. For example,
866        [\P{Any}] did so. (Error in the code for printing property names.)
867    
868    21. An orphan \E inside a character class could cause a crash.
869    
870    22. A repeated capturing bracket such as (A)? could cause a wild memory
871        reference during compilation.
872    
873    23. There are several functions in pcre_compile() that scan along a compiled
874        expression for various reasons (e.g. to see if it's fixed length for look
875        behind). There were bugs in these functions when a repeated \p or \P was
876        present in the pattern. These operators have additional parameters compared
877        with \d, etc, and these were not being taken into account when moving along
878        the compiled data. Specifically:
879    
880        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
881            length.
882    
883        (b) An item such as \pL+ within a repeated group could cause crashes or
884            loops.
885    
886        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
887            "reference to non-existent subpattern" error.
888    
889        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
890    
891    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
892        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
893    
894    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
895    
896    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
897        character were causing crashes (broken optimization).
898    
899    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
900        \p or \P) caused a compile-time loop.
901    
902    28. More problems have arisen in unanchored patterns when CRLF is a valid line
903        break. For example, the unstudied pattern [\r\n]A does not match the string
904        "\r\nA" because change 7.0/46 below moves the current point on by two
905        characters after failing to match at the start. However, the pattern \nA
906        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
907        the same is true. There doesn't seem any very clean way out of this, but
908        what I have chosen to do makes the common cases work: PCRE now takes note
909        of whether there can be an explicit match for \r or \n anywhere in the
910        pattern, and if so, 7.0/46 no longer applies. As part of this change,
911        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
912        pattern has explicit CR or LF references.
913    
914    29. Added (*CR) etc for changing newline setting at start of pattern.
915    
916    
917  Version 7.2 19-Jun-07  Version 7.2 19-Jun-07

Legend:
Removed from v.216  
changed lines
  Added in v.472

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12