ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 122 by ph10, Mon Mar 12 15:10:25 2007 UTC revision 483 by ph10, Mon Jan 4 16:19:17 2010 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.1 12-Mar-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.
71    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
72        messages were output:
74          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
75          rerunning libtoolize, to keep the correct libtool macros in-tree.
76          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
78        I have done both of these things.
80    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
81        most of the time, it *can* run out if it is given a pattern that contains a
82        runaway infinite recursion. I updated the discussion in the pcrestack man
83        page.
85    13. Now that we have gone to the x.xx style of version numbers, the minor
86        version may start with zero. Using 08 or 09 is a bad idea because users
87        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
88        interpreted as invalid octal numbers. I've updated the previous comment in
89        configure.ac, and also added a check that gives an error if 08 or 09 are
90        used.
92    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
93        causing partial matching to fail when the end of the subject matched \W
94        in a UTF-8 pattern where \W was quantified with a minimum of 3.
96    15. There were some discrepancies between the declarations in pcre_internal.h
97        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
98        their definitions. The declarations used "const uschar *" and the
99        definitions used USPTR. Even though USPTR is normally defined as "const
100        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
101        reported that: "This difference in casting confuses some C++ compilers, for
102        example, SunCC recognizes above declarations as different functions and
103        generates broken code for hbpcre." I have changed the declarations to use
104        USPTR.
109    Version 8.00 19-Oct-09
110    ----------------------
112    1.  The table for translating pcre_compile() error codes into POSIX error codes
113        was out-of-date, and there was no check on the pcre_compile() error code
114        being within the table. This could lead to an OK return being given in
115        error.
117    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
118        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
119        in a Windows environment.
121    3.  The pcregrep --count option prints the count for each file even when it is
122        zero, as does GNU grep. However, pcregrep was also printing all files when
123        --files-with-matches was added. Now, when both options are given, it prints
124        counts only for those files that have at least one match. (GNU grep just
125        prints the file name in this circumstance, but including the count seems
126        more useful - otherwise, why use --count?) Also ensured that the
127        combination -clh just lists non-zero counts, with no names.
129    4.  The long form of the pcregrep -F option was incorrectly implemented as
130        --fixed_strings instead of --fixed-strings. This is an incompatible change,
131        but it seems right to fix it, and I didn't think it was worth preserving
132        the old behaviour.
134    5.  The command line items --regex=pattern and --regexp=pattern were not
135        recognized by pcregrep, which required --regex pattern or --regexp pattern
136        (with a space rather than an '='). The man page documented the '=' forms,
137        which are compatible with GNU grep; these now work.
139    6.  No libpcreposix.pc file was created for pkg-config; there was just
140        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
142    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
143        when UCP support is not needed, by modifying the Python script that
144        generates it from Unicode data files. This should not matter if the module
145        is correctly used as a library, but I received one complaint about 50K of
146        unwanted data. My guess is that the person linked everything into his
147        program rather than using a library. Anyway, it does no harm.
149    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
150        was a minimum greater than 1 for a wide character in a possessive
151        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
152        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
153        character. Chaos in the form of incorrect output or a compiling loop could
154        result.
156    9.  The restrictions on what a pattern can contain when partial matching is
157        requested for pcre_exec() have been removed. All patterns can now be
158        partially matched by this function. In addition, if there are at least two
159        slots in the offset vector, the offset of the earliest inspected character
160        for the match and the offset of the end of the subject are set in them when
161        PCRE_ERROR_PARTIAL is returned.
163    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
164        synonymous with PCRE_PARTIAL, for backwards compatibility, and
165        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
166        and may be more useful for multi-segment matching.
168    11. Partial matching with pcre_exec() is now more intuitive. A partial match
169        used to be given if ever the end of the subject was reached; now it is
170        given only if matching could not proceed because another character was
171        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
172        string "Z", which now yields "no match" instead of "partial match". In the
173        case of pcre_dfa_exec(), "no match" is given if every matching path for the
174        final character ended with (*FAIL).
176    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
177        if the pattern had a "must contain" character that was already found in the
178        earlier partial match, unless partial matching was again requested. For
179        example, with the pattern /dog.(body)?/, the "must contain" character is
180        "g". If the first part-match was for the string "dog", restarting with
181        "sbody" failed. This bug has been fixed.
183    13. The string returned by pcre_dfa_exec() after a partial match has been
184        changed so that it starts at the first inspected character rather than the
185        first character of the match. This makes a difference only if the pattern
186        starts with a lookbehind assertion or \b or \B (\K is not supported by
187        pcre_dfa_exec()). It's an incompatible change, but it makes the two
188        matching functions compatible, and I think it's the right thing to do.
190    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
191        so that the demonstration program is easily available in environments where
192        PCRE has not been installed from source.
194    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
195        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
196        library.
198    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
199        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
200        is not the first non-POSIX option to be added. Clearly some people find
201        these options useful.
203    17. If a caller to the POSIX matching function regexec() passes a non-zero
204        value for nmatch with a NULL value for pmatch, the value of
205        nmatch is forced to zero.
207    18. RunGrepTest did not have a test for the availability of the -u option of
208        the diff command, as RunTest does. It now checks in the same way as
209        RunTest, and also checks for the -b option.
211    19. If an odd number of negated classes containing just a single character
212        interposed, within parentheses, between a forward reference to a named
213        subpattern and the definition of the subpattern, compilation crashed with
214        an internal error, complaining that it could not find the referenced
215        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
216        [The bug was that it was starting one character too far in when skipping
217        over the character class, thus treating the ] as data rather than
218        terminating the class. This meant it could skip too much.]
220    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
221        /g option in pcretest when the pattern contains \K, which makes it possible
222        to have an empty string match not at the start, even when the pattern is
223        anchored. Updated pcretest and pcredemo to use this option.
225    21. If the maximum number of capturing subpatterns in a recursion was greater
226        than the maximum at the outer level, the higher number was returned, but
227        with unset values at the outer level. The correct (outer level) value is
228        now given.
230    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
231        PCRE did not set those parentheses (unlike Perl). I have now found a way to
232        make it do so. The string so far is captured, making this feature
233        compatible with Perl.
235    23. The tests have been re-organized, adding tests 11 and 12, to make it
236        possible to check the Perl 5.10 features against Perl 5.10.
238    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
239        pattern matches a fixed length string. PCRE did not allow this; now it
240        does. Neither allows recursion.
242    25. I finally figured out how to implement a request to provide the minimum
243        length of subject string that was needed in order to match a given pattern.
244        (It was back references and recursion that I had previously got hung up
245        on.) This code has now been added to pcre_study(); it finds a lower bound
246        to the length of subject needed. It is not necessarily the greatest lower
247        bound, but using it to avoid searching strings that are too short does give
248        some useful speed-ups. The value is available to calling programs via
249        pcre_fullinfo().
251    26. While implementing 25, I discovered to my embarrassment that pcretest had
252        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
253        study optimizations had never been tested with that matching function.
254        Oops. What is worse, even when it was passed study data, there was a bug in
255        pcre_dfa_exec() that meant it never actually used it. Double oops. There
256        were also very few tests of studied patterns with pcre_dfa_exec().
258    27. If (?| is used to create subpatterns with duplicate numbers, they are now
259        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
260        on the other side of the coin, they are no longer allowed to have different
261        names, because these cannot be distinguished in PCRE, and this has caused
262        confusion. (This is a difference from Perl.)
264    28. When duplicate subpattern names are present (necessarily with different
265        numbers, as required by 27 above), and a test is made by name in a
266        conditional pattern, either for a subpattern having been matched, or for
267        recursion in such a pattern, all the associated numbered subpatterns are
268        tested, and the overall condition is true if the condition is true for any
269        one of them. This is the way Perl works, and is also more like the way
270        testing by number works.
273    Version 7.9 11-Apr-09
274    ---------------------
276    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
277        (pcretest), all targets were linked against these libraries. This included
278        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
279        libraries. This caused unwanted dependencies to be created. This problem
280        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
281        pcretest is linked with readline.
283    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
284        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
285        moved outside it again, because FALSE and TRUE are already defined in AIX,
286        but BOOL is not.
288    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
289        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
291    4.  The pcregrep documentation said spaces were inserted as well as colons (or
292        hyphens) following file names and line numbers when outputting matching
293        lines. This is not true; no spaces are inserted. I have also clarified the
294        wording for the --colour (or --color) option.
296    5.  In pcregrep, when --colour was used with -o, the list of matching strings
297        was not coloured; this is different to GNU grep, so I have changed it to be
298        the same.
300    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
301        each matching line was coloured. Now it goes on to look for further matches
302        of any of the test patterns, which is the same behaviour as GNU grep.
304    7.  A pattern that could match an empty string could cause pcregrep to loop; it
305        doesn't make sense to accept an empty string match in pcregrep, so I have
306        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
307        seems to be how GNU grep behaves.
309    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
310        start or after a newline", because the conditional assertion was not being
311        correctly handled. The rule now is that both the assertion and what follows
312        in the first alternative must satisfy the test.
314    9.  If auto-callout was enabled in a pattern with a conditional group whose
315        condition was an assertion, PCRE could crash during matching, both with
316        pcre_exec() and pcre_dfa_exec().
318    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
319        used for matching.
321    11. Unicode property support in character classes was not working for
322        characters (bytes) greater than 127 when not in UTF-8 mode.
324    12. Added the -M command line option to pcretest.
326    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
328    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
330    16. Added comments and documentation about mis-use of no_arg in the C++
331        wrapper.
333    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
334        from Martin Jerabek that uses macro names for all relevant character and
335        string constants.
337    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
338        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
339        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
340        these, but not everybody uses configure.
342    19. A conditional group that had only one branch was not being correctly
343        recognized as an item that could match an empty string. This meant that an
344        enclosing group might also not be so recognized, causing infinite looping
345        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
346        with the subject "ab", where knowledge that the repeated group can match
347        nothing is needed in order to break the loop.
349    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
350        exec(), but without supplying a callout function, matching went wrong.
352    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
353        leak if the size of the offset vector was greater than 30. When the vector
354        is smaller, the saved offsets during recursion go onto a local stack
355        vector, but for larger vectors malloc() is used. It was failing to free
356        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
357        error, in fact).
359    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
360        heapframe that is used only when UTF-8 support is enabled. This caused no
361        problem, but was untidy.
363    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
364        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
365        included within another project.
367    24. Steven Van Ingelgem's patches to add more options to the CMake support,
368        slightly modified by me:
370          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
371              not building pcregrep.
373          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
374              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
376    25. Forward references, both numeric and by name, in patterns that made use of
377        duplicate group numbers, could behave incorrectly or give incorrect errors,
378        because when scanning forward to find the reference group, PCRE was not
379        taking into account the duplicate group numbers. A pattern such as
380        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
382    26. Changed a few more instances of "const unsigned char *" to USPTR, making
383        the feature of a custom pointer more persuasive (as requested by a user).
385    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
386        pcretest.c, inside #ifndefs, because it seems they are sometimes already
387        pre-defined.
389    28. Added support for (*UTF8) at the start of a pattern.
391    29. Arrange for flags added by the "release type" setting in CMake to be shown
392        in the configuration summary.
395    Version 7.8 05-Sep-08
396    ---------------------
398    1.  Replaced UCP searching code with optimized version as implemented for Ad
399        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
400        stage table and inline lookup instead of a function, giving speed ups of 2
401        to 5 times on some simple patterns that I tested. Permission was given to
402        distribute the MultiStage2.py script that generates the tables (it's not in
403        the tarball, but is in the Subversion repository).
405    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
406        scripts.
408    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
409        a group with a zero qualifier. The result of the study could be incorrect,
410        or the function might crash, depending on the pattern.
412    4.  Caseless matching was not working for non-ASCII characters in back
413        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
414        It now works when Unicode Property Support is available.
416    5.  In pcretest, an escape such as \x{de} in the data was always generating
417        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
418        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
419        truncation.
421    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
423    7.  Added two (int) casts to pcregrep when printing the difference of two
424        pointers, in case they are 64-bit values.
426    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
427        test 2 if it fails.
429    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
430        and a #define of that name to empty if it is not externally set. This is to
431        allow users of MSVC to set it if necessary.
433    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
434        the convenience functions in the pcre_get.c source file.
436    11. An option change at the start of a pattern that had top-level alternatives
437        could cause overwriting and/or a crash. This command provoked a crash in
438        some environments:
440          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
442        This potential security problem was recorded as CVE-2008-2371.
444    12. For a pattern where the match had to start at the beginning or immediately
445        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
446        pcre_dfa_exec() could read past the end of the passed subject if there was
447        no match. To help with detecting such bugs (e.g. with valgrind), I modified
448        pcretest so that it places the subject at the end of its malloc-ed buffer.
450    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
451        exec() might read past the end of the data buffer in UTF-8 mode.
453    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
454        the data contained the byte 0x85 as part of a UTF-8 character within its
455        first line. This applied both to normal and DFA matching.
457    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
458        /^[^d]*?$/8 failed to match "abc".
460    16. Added a missing copyright notice to pcrecpp_internal.h.
462    17. Make it more clear in the documentation that values returned from
463        pcre_exec() in ovector are byte offsets, not character counts.
465    18. Tidied a few places to stop certain compilers from issuing warnings.
467    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
468        supplied by Stefan Weber. I made a further small update for 7.8 because
469        there is a change of source arrangements: the pcre_searchfuncs.c module is
470        replaced by pcre_ucd.c.
473    Version 7.7 07-May-08
474    ---------------------
476    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
477        a string to a long long, pretend we don't even have a long long." This is
478        done by checking for the strtoq, strtoll, and _strtoi64 functions.
480    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
481        pre-7.6 versions, which defined a global no_arg variable instead of putting
482        it in the RE class. (See also #8 below.)
484    3.  Remove a line of dead code, identified by coverity and reported by Nuno
485        Lopes.
487    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
489        (1) The include/exclude patterns were being applied to the whole pathnames
490            of files, instead of just to the final components.
492        (2) If there was more than one level of directory, the subdirectories were
493            skipped unless they satisfied the include/exclude conditions. This is
494            inconsistent with GNU grep (and could even be seen as contrary to the
495            pcregrep specification - which I improved to make it absolutely clear).
496            The action now is always to scan all levels of directory, and just
497            apply the include/exclude patterns to regular files.
499    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
500        --exclude_dir in the tests to avoid scanning .svn directories.
502    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
503        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
504        doesn't support NULs in patterns.
506    7.  Added some missing "const"s to declarations of static tables in
507        pcre_compile.c and pcre_dfa_exec.c.
509    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
510        caused by fix #2  above. (Subsequently also a second patch to fix the
511        first patch. And a third patch - this was a messy problem.)
513    9.  Applied Craig's patch to remove the use of push_back().
515    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
516        matching function regexec().
518    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
519        which, however, unlike Perl's \g{...}, are subroutine calls, not back
520        references. PCRE supports relative numbers with this syntax (I don't think
521        Oniguruma does).
523    12. Previously, a group with a zero repeat such as (...){0} was completely
524        omitted from the compiled regex. However, this means that if the group
525        was called as a subroutine from elsewhere in the pattern, things went wrong
526        (an internal error was given). Such groups are now left in the compiled
527        pattern, with a new opcode that causes them to be skipped at execution
528        time.
530    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
531        to the way PCRE behaves:
533        (a) A lone ] character is dis-allowed (Perl treats it as data).
535        (b) A back reference to an unmatched subpattern matches an empty string
536            (Perl fails the current match path).
538        (c) A data ] in a character class must be notated as \] because if the
539            first data character in a class is ], it defines an empty class. (In
540            Perl it is not possible to have an empty class.) The empty class []
541            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
542            The negative empty class [^] matches any one character, independently
543            of the DOTALL setting.
545    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
546        non-existent subpattern following a character class starting with ']' and
547        containing () gave an internal compiling error instead of "reference to
548        non-existent subpattern". Fortunately, when the pattern did exist, the
549        compiled code was correct. (When scanning forwards to check for the
550        existencd of the subpattern, it was treating the data ']' as terminating
551        the class, so got the count wrong. When actually compiling, the reference
552        was subsequently set up correctly.)
554    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
555        it was being rejected as not supported by pcre_dfa_exec(), even though
556        other assertions are supported. I have made pcre_dfa_exec() support
557        (*FAIL).
559    16. The implementation of 13c above involved the invention of a new opcode,
560        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
561        cannot be changed at match time, I realized I could make a small
562        improvement to matching performance by compiling OP_ALLANY instead of
563        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
564        on the OP_ANY path.
566    17. Compiling pcretest on Windows with readline support failed without the
567        following two fixes: (1) Make the unistd.h include conditional on
568        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
570    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
571        ncurses library to be included for pcretest when ReadLine support is
572        requested, but also to allow for it to be overridden. This patch came from
573        Daniel Bergström.
575    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
576        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
577        any errors with the current Unicode tables. Thanks to Peter Kankowski for
578        spotting this.
581    Version 7.6 28-Jan-08
582    ---------------------
584    1.  A character class containing a very large number of characters with
585        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
586        overflow.
588    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
589        HAVE_LONG_LONG is not defined.
591    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
592        bring them up to date and include new features. This patch includes:
594        - Fixed PH's badly added libz and libbz2 support.
595        - Fixed a problem with static linking.
596        - Added pcredemo. [But later removed - see 7 below.]
597        - Fixed dftables problem and added an option.
598        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
599            HAVE_LONG_LONG.
600        - Added readline support for pcretest.
601        - Added an listing of the option settings after cmake has run.
603    4.  A user submitted a patch to Makefile that makes it easy to create
604        "pcre.dll" under mingw when using Configure/Make. I added stuff to
605        Makefile.am that cause it to include this special target, without
606        affecting anything else. Note that the same mingw target plus all
607        the other distribution libraries and programs are now supported
608        when configuring with CMake (see 6 below) instead of with
609        Configure/Make.
611    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
612        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
613        exported in the Windows port". It has not yet been confirmed that the patch
614        solves the problem, but it does no harm.
616    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
617        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
618        with CMake, and also correct the comment about stack recursion.
620    7.  Remove the automatic building of pcredemo from the ./configure system and
621        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
622        of a program that users should build themselves after PCRE is installed, so
623        building it automatically is not really right. What is more, it gave
624        trouble in some build environments.
626    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
629    Version 7.5 10-Jan-08
630    ---------------------
632    1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
633        values in parens when parsing an RE using the C++ wrapper."
635    2.  Negative specials like \S did not work in character classes in UTF-8 mode.
636        Characters greater than 255 were excluded from the class instead of being
637        included.
639    3.  The same bug as (2) above applied to negated POSIX classes such as
640        [:^space:].
642    4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
643        defined or documented. It seems to have been a typo for PCRE_STATIC, so
644        I have changed it.
646    5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
647        first named subpattern) and a construct such as (?&a) would reference the
648        first named subpattern whose name started with "a" (in other words, the
649        length check was missing). Both these problems are fixed. "Subpattern name
650        expected" is now given for (?&) (a zero-length name), and this patch also
651        makes it give the same error for \k'' (previously it complained that that
652        was a reference to a non-existent subpattern).
654    6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
655        this is right because (?- can be followed by option settings as well as by
656        digits. I have, however, made the messages clearer.
658    7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
659        than the number used in the conditional) now cause a compile-time error.
660        This is actually not compatible with Perl, which accepts such patterns, but
661        treats the conditional as always being FALSE (as PCRE used to), but it
662        seems to me that giving a diagnostic is better.
664    8.  Change "alphameric" to the more common word "alphanumeric" in comments
665        and messages.
667    9.  Fix two occurrences of "backslash" in comments that should have been
668        "backspace".
670    10. Remove two redundant lines of code that can never be obeyed (their function
671        was moved elsewhere).
673    11. The program that makes PCRE's Unicode character property table had a bug
674        which caused it to generate incorrect table entries for sequences of
675        characters that have the same character type, but are in different scripts.
676        It amalgamated them into a single range, with the script of the first of
677        them. In other words, some characters were in the wrong script. There were
678        thirteen such cases, affecting characters in the following ranges:
680          U+002b0 - U+002c1
681          U+0060c - U+0060d
682          U+0061e - U+00612
683          U+0064b - U+0065e
684          U+0074d - U+0076d
685          U+01800 - U+01805
686          U+01d00 - U+01d77
687          U+01d9b - U+01dbf
688          U+0200b - U+0200f
689          U+030fc - U+030fe
690          U+03260 - U+0327f
691          U+0fb46 - U+0fbb1
692          U+10450 - U+1049d
694    12. The -o option (show only the matching part of a line) for pcregrep was not
695        compatible with GNU grep in that, if there was more than one match in a
696        line, it showed only the first of them. It now behaves in the same way as
697        GNU grep.
699    13. If the -o and -v options were combined for pcregrep, it printed a blank
700        line for every non-matching line. GNU grep prints nothing, and pcregrep now
701        does the same. The return code can be used to tell if there were any
702        non-matching lines.
704    14. Added --file-offsets and --line-offsets to pcregrep.
706    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
707        infinitely looping recursion. The bug was that positive lookaheads were not
708        being skipped when checking for a possible empty match (negative lookaheads
709        and both kinds of lookbehind were skipped).
711    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
712        inclusion of <windows.h> to before rather than after the definition of
713        INVALID_FILE_ATTRIBUTES (patch from David Byron).
715    17. Specifying a possessive quantifier with a specific limit for a Unicode
716        character property caused pcre_compile() to compile bad code, which led at
717        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
718        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
719        caused the error; without that there was no problem.
721    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
723    19. Added --enable-pcretest-libreadline.
725    20. In pcrecpp.cc, the variable 'count' was incremented twice in
726        RE::GlobalReplace(). As a result, the number of replacements returned was
727        double what it should be. I removed one of the increments, but Craig sent a
728        later patch that removed the other one (the right fix) and added unit tests
729        that check the return values (which was not done before).
731    21. Several CMake things:
733        (1) Arranged that, when cmake is used on Unix, the libraries end up with
734            the names libpcre and libpcreposix, not just pcre and pcreposix.
736        (2) The above change means that pcretest and pcregrep are now correctly
737            linked with the newly-built libraries, not previously installed ones.
741    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
742        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
743        UTF-8 newline character). The key issue is that the pattern starts .*;
744        this means that the match must be either at the beginning, or after a
745        newline. The bug was in the code for advancing after a failed match and
746        checking that the new position followed a newline. It was not taking
747        account of UTF-8 characters correctly.
749    23. PCRE was behaving differently from Perl in the way it recognized POSIX
750        character classes. PCRE was not treating the sequence [:...:] as a
751        character class unless the ... were all letters. Perl, however, seems to
752        allow any characters between [: and :], though of course it rejects as
753        unknown any "names" that contain non-letters, because all the known class
754        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
755        for example, whereas PCRE did not - it did not recognize a POSIX character
756        class. This seemed a bit dangerous, so the code has been changed to be
757        closer to Perl. The behaviour is not identical to Perl, because PCRE will
758        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
759        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
760        Perl does, and where it didn't before.
762    24. Rewrite so as to remove the single use of %n from pcregrep because in some
763        Windows environments %n is disabled by default.
766    Version 7.4 21-Sep-07
767    ---------------------
769    1.  Change 7.3/28 was implemented for classes by looking at the bitmap. This
770        means that a class such as [\s] counted as "explicit reference to CR or
771        LF". That isn't really right - the whole point of the change was to try to
772        help when there was an actual mention of one of the two characters. So now
773        the change happens only if \r or \n (or a literal CR or LF) character is
774        encountered.
776    2.  The 32-bit options word was also used for 6 internal flags, but the numbers
777        of both had grown to the point where there were only 3 bits left.
778        Fortunately, there was spare space in the data structure, and so I have
779        moved the internal flags into a new 16-bit field to free up more option
780        bits.
782    3.  The appearance of (?J) at the start of a pattern set the DUPNAMES option,
783        but did not set the internal JCHANGED flag - either of these is enough to
784        control the way the "get" function works - but the PCRE_INFO_JCHANGED
785        facility is supposed to tell if (?J) was ever used, so now (?J) at the
786        start sets both bits.
788    4.  Added options (at build time, compile time, exec time) to change \R from
789        matching any Unicode line ending sequence to just matching CR, LF, or CRLF.
791    5.  doc/pcresyntax.html was missing from the distribution.
793    6.  Put back the definition of PCRE_ERROR_NULLWSLIMIT, for backward
794        compatibility, even though it is no longer used.
796    7.  Added macro for snprintf to pcrecpp_unittest.cc and also for strtoll and
797        strtoull to pcrecpp.cc to select the available functions in WIN32 when the
798        windows.h file is present (where different names are used). [This was
799        reversed later after testing - see 16 below.]
801    8.  Changed all #include <config.h> to #include "config.h". There were also
802        some further <pcre.h> cases that I changed to "pcre.h".
804    9.  When pcregrep was used with the --colour option, it missed the line ending
805        sequence off the lines that it output.
807    10. It was pointed out to me that arrays of string pointers cause lots of
808        relocations when a shared library is dynamically loaded. A technique of
809        using a single long string with a table of offsets can drastically reduce
810        these. I have refactored PCRE in four places to do this. The result is
811        dramatic:
813          Originally:                          290
814          After changing UCP table:            187
815          After changing error message table:   43
816          After changing table of "verbs"       36
817          After changing table of Posix names   22
819        Thanks to the folks working on Gregex for glib for this insight.
821    11. --disable-stack-for-recursion caused compiling to fail unless -enable-
822        unicode-properties was also set.
824    12. Updated the tests so that they work when \R is defaulted to ANYCRLF.
826    13. Added checks for ANY and ANYCRLF to pcrecpp.cc where it previously
827        checked only for CRLF.
829    14. Added casts to pcretest.c to avoid compiler warnings.
831    15. Added Craig's patch to various pcrecpp modules to avoid compiler warnings.
833    16. Added Craig's patch to remove the WINDOWS_H tests, that were not working,
834        and instead check for _strtoi64 explicitly, and avoid the use of snprintf()
835        entirely. This removes changes made in 7 above.
837    17. The CMake files have been updated, and there is now more information about
838        building with CMake in the NON-UNIX-USE document.
841    Version 7.3 28-Aug-07
842    ---------------------
844     1. In the rejigging of the build system that eventually resulted in 7.1, the
845        line "#include <pcre.h>" was included in pcre_internal.h. The use of angle
846        brackets there is not right, since it causes compilers to look for an
847        installed pcre.h, not the version that is in the source that is being
848        compiled (which of course may be different). I have changed it back to:
850          #include "pcre.h"
852        I have a vague recollection that the change was concerned with compiling in
853        different directories, but in the new build system, that is taken care of
854        by the VPATH setting the Makefile.
856     2. The pattern .*$ when run in not-DOTALL UTF-8 mode with newline=any failed
857        when the subject happened to end in the byte 0x85 (e.g. if the last
858        character was \x{1ec5}). *Character* 0x85 is one of the "any" newline
859        characters but of course it shouldn't be taken as a newline when it is part
860        of another character. The bug was that, for an unlimited repeat of . in
861        not-DOTALL UTF-8 mode, PCRE was advancing by bytes rather than by
862        characters when looking for a newline.
864     3. A small performance improvement in the DOTALL UTF-8 mode .* case.
866     4. Debugging: adjusted the names of opcodes for different kinds of parentheses
867        in debug output.
869     5. Arrange to use "%I64d" instead of "%lld" and "%I64u" instead of "%llu" for
870        long printing in the pcrecpp unittest when running under MinGW.
872     6. ESC_K was left out of the EBCDIC table.
874     7. Change 7.0/38 introduced a new limit on the number of nested non-capturing
875        parentheses; I made it 1000, which seemed large enough. Unfortunately, the
876        limit also applies to "virtual nesting" when a pattern is recursive, and in
877        this case 1000 isn't so big. I have been able to remove this limit at the
878        expense of backing off one optimization in certain circumstances. Normally,
879        when pcre_exec() would call its internal match() function recursively and
880        immediately return the result unconditionally, it uses a "tail recursion"
881        feature to save stack. However, when a subpattern that can match an empty
882        string has an unlimited repetition quantifier, it no longer makes this
883        optimization. That gives it a stack frame in which to save the data for
884        checking that an empty string has been matched. Previously this was taken
885        from the 1000-entry workspace that had been reserved. So now there is no
886        explicit limit, but more stack is used.
888     8. Applied Daniel's patches to solve problems with the import/export magic
889        syntax that is required for Windows, and which was going wrong for the
890        pcreposix and pcrecpp parts of the library. These were overlooked when this
891        problem was solved for the main library.
893     9. There were some crude static tests to avoid integer overflow when computing
894        the size of patterns that contain repeated groups with explicit upper
895        limits. As the maximum quantifier is 65535, the maximum group length was
896        set at 30,000 so that the product of these two numbers did not overflow a
897        32-bit integer. However, it turns out that people want to use groups that
898        are longer than 30,000 bytes (though not repeat them that many times).
899        Change 7.0/17 (the refactoring of the way the pattern size is computed) has
900        made it possible to implement the integer overflow checks in a much more
901        dynamic way, which I have now done. The artificial limitation on group
902        length has been removed - we now have only the limit on the total length of
903        the compiled pattern, which depends on the LINK_SIZE setting.
905    10. Fixed a bug in the documentation for get/copy named substring when
906        duplicate names are permitted. If none of the named substrings are set, the
907        functions return PCRE_ERROR_NOSUBSTRING (7); the doc said they returned an
908        empty string.
910    11. Because Perl interprets \Q...\E at a high level, and ignores orphan \E
911        instances, patterns such as [\Q\E] or [\E] or even [^\E] cause an error,
912        because the ] is interpreted as the first data character and the
913        terminating ] is not found. PCRE has been made compatible with Perl in this
914        regard. Previously, it interpreted [\Q\E] as an empty class, and [\E] could
915        cause memory overwriting.
917    10. Like Perl, PCRE automatically breaks an unlimited repeat after an empty
918        string has been matched (to stop an infinite loop). It was not recognizing
919        a conditional subpattern that could match an empty string if that
920        subpattern was within another subpattern. For example, it looped when
921        trying to match  (((?(1)X|))*)  but it was OK with  ((?(1)X|)*)  where the
922        condition was not nested. This bug has been fixed.
924    12. A pattern like \X?\d or \P{L}?\d in non-UTF-8 mode could cause a backtrack
925        past the start of the subject in the presence of bytes with the top bit
926        set, for example "\x8aBCD".
928    13. Added Perl 5.10 experimental backtracking controls (*FAIL), (*F), (*PRUNE),
929        (*SKIP), (*THEN), (*COMMIT), and (*ACCEPT).
931    14. Optimized (?!) to (*FAIL).
933    15. Updated the test for a valid UTF-8 string to conform to the later RFC 3629.
934        This restricts code points to be within the range 0 to 0x10FFFF, excluding
935        the "low surrogate" sequence 0xD800 to 0xDFFF. Previously, PCRE allowed the
936        full range 0 to 0x7FFFFFFF, as defined by RFC 2279. Internally, it still
937        does: it's just the validity check that is more restrictive.
939    16. Inserted checks for integer overflows during escape sequence (backslash)
940        processing, and also fixed erroneous offset values for syntax errors during
941        backslash processing.
943    17. Fixed another case of looking too far back in non-UTF-8 mode (cf 12 above)
944        for patterns like [\PPP\x8a]{1,}\x80 with the subject "A\x80".
946    18. An unterminated class in a pattern like (?1)\c[ with a "forward reference"
947        caused an overrun.
949    19. A pattern like (?:[\PPa*]*){8,} which had an "extended class" (one with
950        something other than just ASCII characters) inside a group that had an
951        unlimited repeat caused a loop at compile time (while checking to see
952        whether the group could match an empty string).
954    20. Debugging a pattern containing \p or \P could cause a crash. For example,
955        [\P{Any}] did so. (Error in the code for printing property names.)
957    21. An orphan \E inside a character class could cause a crash.
959    22. A repeated capturing bracket such as (A)? could cause a wild memory
960        reference during compilation.
962    23. There are several functions in pcre_compile() that scan along a compiled
963        expression for various reasons (e.g. to see if it's fixed length for look
964        behind). There were bugs in these functions when a repeated \p or \P was
965        present in the pattern. These operators have additional parameters compared
966        with \d, etc, and these were not being taken into account when moving along
967        the compiled data. Specifically:
969        (a) A item such as \p{Yi}{3} in a lookbehind was not treated as fixed
970            length.
972        (b) An item such as \pL+ within a repeated group could cause crashes or
973            loops.
975        (c) A pattern such as \p{Yi}+(\P{Yi}+)(?1) could give an incorrect
976            "reference to non-existent subpattern" error.
978        (d) A pattern like (\P{Yi}{2}\277)? could loop at compile time.
980    24. A repeated \S or \W in UTF-8 mode could give wrong answers when multibyte
981        characters were involved (for example /\S{2}/8g with "A\x{a3}BC").
983    25. Using pcregrep in multiline, inverted mode (-Mv) caused it to loop.
985    26. Patterns such as [\P{Yi}A] which include \p or \P and just one other
986        character were causing crashes (broken optimization).
988    27. Patterns such as (\P{Yi}*\277)* (group with possible zero repeat containing
989        \p or \P) caused a compile-time loop.
991    28. More problems have arisen in unanchored patterns when CRLF is a valid line
992        break. For example, the unstudied pattern [\r\n]A does not match the string
993        "\r\nA" because change 7.0/46 below moves the current point on by two
994        characters after failing to match at the start. However, the pattern \nA
995        *does* match, because it doesn't start till \n, and if [\r\n]A is studied,
996        the same is true. There doesn't seem any very clean way out of this, but
997        what I have chosen to do makes the common cases work: PCRE now takes note
998        of whether there can be an explicit match for \r or \n anywhere in the
999        pattern, and if so, 7.0/46 no longer applies. As part of this change,
1000        there's a new PCRE_INFO_HASCRORLF option for finding out whether a compiled
1001        pattern has explicit CR or LF references.
1003    29. Added (*CR) etc for changing newline setting at start of pattern.
1006    Version 7.2 19-Jun-07
1007    ---------------------
1009     1. If the fr_FR locale cannot be found for test 3, try the "french" locale,
1010        which is apparently normally available under Windows.
1012     2. Re-jig the pcregrep tests with different newline settings in an attempt
1013        to make them independent of the local environment's newline setting.
1015     3. Add code to configure.ac to remove -g from the CFLAGS default settings.
1017     4. Some of the "internals" tests were previously cut out when the link size
1018        was not 2, because the output contained actual offsets. The recent new
1019        "Z" feature of pcretest means that these can be cut out, making the tests
1020        usable with all link sizes.
1022     5. Implemented Stan Switzer's goto replacement for longjmp() when not using
1023        stack recursion. This gives a massive performance boost under BSD, but just
1024        a small improvement under Linux. However, it saves one field in the frame
1025        in all cases.
1027     6. Added more features from the forthcoming Perl 5.10:
1029        (a) (?-n) (where n is a string of digits) is a relative subroutine or
1030            recursion call. It refers to the nth most recently opened parentheses.
1032        (b) (?+n) is also a relative subroutine call; it refers to the nth next
1033            to be opened parentheses.
1035        (c) Conditions that refer to capturing parentheses can be specified
1036            relatively, for example, (?(-2)... or (?(+3)...
1038        (d) \K resets the start of the current match so that everything before
1039            is not part of it.
1041        (e) \k{name} is synonymous with \k<name> and \k'name' (.NET compatible).
1043        (f) \g{name} is another synonym - part of Perl 5.10's unification of
1044            reference syntax.
1046        (g) (?| introduces a group in which the numbering of parentheses in each
1047            alternative starts with the same number.
1049        (h) \h, \H, \v, and \V match horizontal and vertical whitespace.
1051     7. Added two new calls to pcre_fullinfo(): PCRE_INFO_OKPARTIAL and
1054     8. A pattern such as  (.*(.)?)*  caused pcre_exec() to fail by either not
1055        terminating or by crashing. Diagnosed by Viktor Griph; it was in the code
1056        for detecting groups that can match an empty string.
1058     9. A pattern with a very large number of alternatives (more than several
1059        hundred) was running out of internal workspace during the pre-compile
1060        phase, where pcre_compile() figures out how much memory will be needed. A
1061        bit of new cunning has reduced the workspace needed for groups with
1062        alternatives. The 1000-alternative test pattern now uses 12 bytes of
1063        workspace instead of running out of the 4096 that are available.
1065    10. Inserted some missing (unsigned int) casts to get rid of compiler warnings.
1067    11. Applied patch from Google to remove an optimization that didn't quite work.
1068        The report of the bug said:
1070          pcrecpp::RE("a*").FullMatch("aaa") matches, while
1071          pcrecpp::RE("a*?").FullMatch("aaa") does not, and
1072          pcrecpp::RE("a*?\\z").FullMatch("aaa") does again.
1074    12. If \p or \P was used in non-UTF-8 mode on a character greater than 127
1075        it matched the wrong number of bytes.
1078    Version 7.1 24-Apr-07
1079  ---------------------  ---------------------
1081   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one   1. Applied Bob Rossi and Daniel G's patches to convert the build system to one
# Line 26  Version 7.1 12-Mar-07 Line 1100  Version 7.1 12-Mar-07
1100      .br or .in.      .br or .in.
1102   4. Updated comments in configure.ac that get placed in config.h.in and also   4. Updated comments in configure.ac that get placed in config.h.in and also
1103      arranged for config.h to be included in the distribution, with the name      arranged for config.h to be included in the distribution, with the name
1104      config.h.generic, for the benefit of those who have to compile without      config.h.generic, for the benefit of those who have to compile without
1105      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).      Autotools (compare pcre.h, which is now distributed as pcre.h.generic).
1107   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan   5. Updated the support (such as it is) for Virtual Pascal, thanks to Stefan
1108      Weber: (1) pcre_internal.h was missing some function renames; (2) updated      Weber: (1) pcre_internal.h was missing some function renames; (2) updated
1109      makevp.bat for the current PCRE, using the additional files !compile.txt,      makevp.bat for the current PCRE, using the additional files
1110      !linklib.txt, and pcregexp.pas.      makevp_c.txt, makevp_l.txt, and pcregexp.pas.
1112   6. A Windows user reported a minor discrepancy with test 2, which turned out   6. A Windows user reported a minor discrepancy with test 2, which turned out
1113      to be caused by a trailing space on an input line that had got lost in his      to be caused by a trailing space on an input line that had got lost in his
# Line 63  Version 7.1 12-Mar-07 Line 1137  Version 7.1 12-Mar-07
1137  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:  10. Fixed two bugs in the emulated memmove() function in pcre_internal.h:
1139      (a) It was defining its arguments as char * instead of void *.      (a) It was defining its arguments as char * instead of void *.
1141      (b) It was assuming that all moves were upwards in memory; this was true      (b) It was assuming that all moves were upwards in memory; this was true
1142          a long time ago when I wrote it, but is no longer the case.          a long time ago when I wrote it, but is no longer the case.
1144      The emulated memove() is provided for those environments that have neither      The emulated memove() is provided for those environments that have neither
1145      memmove() nor bcopy(). I didn't think anyone used it these days, but that      memmove() nor bcopy(). I didn't think anyone used it these days, but that
1146      is clearly not the case, as these two bugs were recently reported.      is clearly not the case, as these two bugs were recently reported.
1148  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,  11. The script PrepareRelease is now distributed: it calls 132html, CleanTxt,
1149      and Detrail to create the HTML documentation, the .txt form of the man      and Detrail to create the HTML documentation, the .txt form of the man
1150      pages, and it removes trailing spaces from listed files. It also creates      pages, and it removes trailing spaces from listed files. It also creates
1151      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter      pcre.h.generic and config.h.generic from pcre.h and config.h. In the latter
1152      case, it wraps all the #defines with #ifndefs. This script should be run      case, it wraps all the #defines with #ifndefs. This script should be run
1153      before "make dist".      before "make dist".
1155  12. Fixed two fairly obscure bugs concerned with quantified caseless matching  12. Fixed two fairly obscure bugs concerned with quantified caseless matching
1156      with Unicode property support.      with Unicode property support.
1158      (a) For a maximizing quantifier, if the two different cases of the      (a) For a maximizing quantifier, if the two different cases of the
1159          character were of different lengths in their UTF-8 codings (there are          character were of different lengths in their UTF-8 codings (there are
1160          some cases like this - I found 11), and the matching function had to          some cases like this - I found 11), and the matching function had to
1161          back up over a mixture of the two cases, it incorrectly assumed they          back up over a mixture of the two cases, it incorrectly assumed they
1162          were both the same length.          were both the same length.
1164      (b) When PCRE was configured to use the heap rather than the stack for      (b) When PCRE was configured to use the heap rather than the stack for
1165          recursion during matching, it was not correctly preserving the data for          recursion during matching, it was not correctly preserving the data for
1166          the other case of a UTF-8 character when checking ahead for a match          the other case of a UTF-8 character when checking ahead for a match
1167          while processing a minimizing repeat. If the check also involved          while processing a minimizing repeat. If the check also involved
1168          matching a wide character, but failed, corruption could cause an          matching a wide character, but failed, corruption could cause an
1169          erroneous result when trying to check for a repeat of the original          erroneous result when trying to check for a repeat of the original
1170          character.          character.
1172  13. Some tidying changes to the testing mechanism:  13. Some tidying changes to the testing mechanism:
1174      (a) The RunTest script now detects the internal link size and whether there      (a) The RunTest script now detects the internal link size and whether there
1175          is UTF-8 and UCP support by running ./pcretest -C instead of relying on          is UTF-8 and UCP support by running ./pcretest -C instead of relying on
1176          values substituted by "configure". (The RunGrepTest script already did          values substituted by "configure". (The RunGrepTest script already did
1177          this for UTF-8.) The configure.ac script no longer substitutes the          this for UTF-8.) The configure.ac script no longer substitutes the
1178          relevant variables.          relevant variables.
1180      (b) The debugging options /B and /D in pcretest show the compiled bytecode      (b) The debugging options /B and /D in pcretest show the compiled bytecode
1181          with length and offset values. This means that the output is different          with length and offset values. This means that the output is different
1182          for different internal link sizes. Test 2 is skipped for link sizes          for different internal link sizes. Test 2 is skipped for link sizes
1183          other than 2 because of this, bypassing the problem. Unfortunately,          other than 2 because of this, bypassing the problem. Unfortunately,
1184          there was also a test in test 3 (the locale tests) that used /B and          there was also a test in test 3 (the locale tests) that used /B and
1185          failed for link sizes other than 2. Rather than cut the whole test out,          failed for link sizes other than 2. Rather than cut the whole test out,
1186          I have added a new /Z option to pcretest that replaces the length and          I have added a new /Z option to pcretest that replaces the length and
1187          offset values with spaces. This is now used to make test 3 independent          offset values with spaces. This is now used to make test 3 independent
1188          of link size. (Test 2 will be tidied up later.)          of link size. (Test 2 will be tidied up later.)
1190  14. If erroroffset was passed as NULL to pcre_compile, it provoked a  14. If erroroffset was passed as NULL to pcre_compile, it provoked a
1191      segmentation fault instead of returning the appropriate error message.      segmentation fault instead of returning the appropriate error message.
1193    15. In multiline mode when the newline sequence was set to "any", the pattern
1194        ^$ would give a match between the \r and \n of a subject such as "A\r\nB".
1195        This doesn't seem right; it now treats the CRLF combination as the line
1196        ending, and so does not match in that case. It's only a pattern such as ^$
1197        that would hit this one: something like ^ABC$ would have failed after \r
1198        and then tried again after \r\n.
1200    16. Changed the comparison command for RunGrepTest from "diff -u" to "diff -ub"
1201        in an attempt to make files that differ only in their line terminators
1202        compare equal. This works on Linux.
1204    17. Under certain error circumstances pcregrep might try to free random memory
1205        as it exited. This is now fixed, thanks to valgrind.
1207    19. In pcretest, if the pattern /(?m)^$/g<any> was matched against the string
1208        "abc\r\n\r\n", it found an unwanted second match after the second \r. This
1209        was because its rules for how to advance for /g after matching an empty
1210        string at the end of a line did not allow for this case. They now check for
1211        it specially.
1213    20. pcretest is supposed to handle patterns and data of any length, by
1214        extending its buffers when necessary. It was getting this wrong when the
1215        buffer for a data line had to be extended.
1217    21. Added PCRE_NEWLINE_ANYCRLF which is like ANY, but matches only CR, LF, or
1218        CRLF as a newline sequence.
1220    22. Code for handling Unicode properties in pcre_dfa_exec() wasn't being cut
1221        out by #ifdef SUPPORT_UCP. This did no harm, as it could never be used, but
1222        I have nevertheless tidied it up.
1224    23. Added some casts to kill warnings from HP-UX ia64 compiler.
1226    24. Added a man page for pcre-config.
1229  Version 7.0 19-Dec-06  Version 7.0 19-Dec-06
1230  ---------------------  ---------------------

Removed from v.122  
changed lines
  Added in v.483

  ViewVC Help
Powered by ViewVC 1.1.5