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

Diff of /code/trunk/ChangeLog

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

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

Legend:
Removed from v.190  
changed lines
  Added in v.469

webmaster@exim.org
ViewVC Help
Powered by ViewVC 1.1.12