ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.168  
changed lines
  Added in v.478

  ViewVC Help
Powered by ViewVC 1.1.5