ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 282 by ph10, Fri Dec 7 19:32:32 2007 UTC revision 611 by ph10, Wed Jun 29 08:49:21 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 7.5 12-Nov-07  Version 8.13 30-Apr-2011
5    ------------------------
7    1.  The Unicode data tables have been updated to Unicode 6.0.0.
9    2.  Two minor typos in pcre_internal.h have been fixed.
11    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
12        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
13        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
15    4.  There were a number of related bugs in the code for matching backrefences
16        caselessly in UTF-8 mode when codes for the characters concerned were
17        different numbers of bytes. For example, U+023A and U+2C65 are an upper
18        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
19        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
20        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
21        2-byte code at the end of the subject (it thought there wasn't enough data
22        left).
24    5.  Comprehensive information about what went wrong is now returned by
25        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
26        as the output vector has at least 2 elements. The offset of the start of
27        the failing character and a reason code are placed in the vector.
29    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
30        now returned is for the first byte of the failing character, instead of the
31        last byte inspected. This is an incompatible change, but I hope it is small
32        enough not to be a problem. It makes the returned offset consistent with
33        pcre_exec() and pcre_dfa_exec().
35    7.  pcretest now gives a text phrase as well as the error number when
36        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
37        failure, the offset and reason code are output.
39    8.  When \R was used with a maximizing quantifier it failed to skip backwards
40        over a \r\n pair if the subsequent match failed. Instead, it just skipped
41        back over a single character (\n). This seems wrong (because it treated the
42        two characters as a single entity when going forwards), conflicts with the
43        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
44        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
45        has been changed.
47    9.  Some internal refactoring has changed the processing so that the handling
48        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
49        time (the PCRE_DOTALL option was changed this way some time ago: version
50        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
51        which was always a bit of a fudge. It also means that there is one less
52        argument for the match() function, which reduces its stack requirements
53        slightly. This change also fixes an incompatibility with Perl: the pattern
54        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
56    10. More internal refactoring has drastically reduced the number of recursive
57        calls to match() for possessively repeated groups such as (abc)++ when
58        using pcre_exec().
60    11. While implementing 10, a number of bugs in the handling of groups were
61        discovered and fixed:
63        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
64        (a|)*(?1) gave a compile-time internal error.
65        ((a|)+)+  did not notice that the outer group could match an empty string.
66        (^a|^)+   was not marked as anchored.
67        (.*a|.*)+ was not marked as matching at start or after a newline.
69    12. Yet more internal refactoring has removed another argument from the match()
70        function. Special calls to this function are now indicated by setting a
71        value in a variable in the "match data" data block.
73    13. Be more explicit in pcre_study() instead of relying on "default" for
74        opcodes that mean there is no starting character; this means that when new
75        ones are added and accidentally left out of pcre_study(), testing should
76        pick them up.
78    14. The -s option of pcretest has been documented for ages as being an old
79        synonym of -m (show memory usage). I have changed it to mean "force study
80        for every regex", that is, assume /S for every regex. This is similar to -i
81        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
82        using it. It makes it easier to run collection of tests with study enabled,
83        and thereby test pcre_study() more easily.
85    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
86        restoration of the capturing data to the outer values was not happening
87        correctly.
89    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
90        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
91        pattern had matched an empty string, and so incorrectly returned a no
92        match.
94    17. There was optimizing code for the last branch of non-capturing parentheses,
95        and also for the obeyed branch of a conditional subexpression, which used
96        tail recursion to cut down on stack usage. Unfortunately, not that there is
97        the possibility of (*THEN) occurring in these branches, tail recursion is
98        no longer possible because the return has to be checked for (*THEN). These
99        two optimizations have therefore been removed.
101    18. If a pattern containing \R was studied, it was assumed that \R always
102        matched two bytes, thus causing the minimum subject length to be
103        incorrectly computed because \R can also match just one byte.
106    Version 8.12 15-Jan-2011
107    ------------------------
109    1.  Fixed some typos in the markup of the man pages, and wrote a script that
110        checks for such things as part of the documentation building process.
112    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
113        --match-limit and --recursion-limit options (added for 8.11). In
114        particular, this made one of the standard tests fail. (The integer value
115        went into the wrong half of a long int.)
117    3.  If the --colour option was given to pcregrep with -v (invert match), it
118        did strange things, either producing crazy output, or crashing. It should,
119        of course, ignore a request for colour when reporting lines that do not
120        match.
122    4.  Another pcregrep bug caused similar problems if --colour was specified with
123        -M (multiline) and the pattern match finished with a line ending.
125    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
126        matched in multiline mode, the following line was shown as part of the
127        match. This seems wrong, so I have changed it.
129    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
130        the check for further matches in the same line (so they could be coloured)
131        to overrun the end of the current line. If another match was found, it was
132        incorrectly shown (and then shown again when found in the next line).
134    7.  If pcregrep was compiled under Windows, there was a reference to the
135        function pcregrep_exit() before it was defined. I am assuming this was
136        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
137        reported by a user. I've moved the definition above the reference.
140    Version 8.11 10-Dec-2010
141    ------------------------
143    1.  (*THEN) was not working properly if there were untried alternatives prior
144        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
145        backtracked to try for "b" instead of moving to the next alternative branch
146        at the same level (in this case, to look for "c"). The Perl documentation
147        is clear that when (*THEN) is backtracked onto, it goes to the "next
148        alternative in the innermost enclosing group".
150    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
151        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
152        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
153        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
154        (*THEN).
156    3.  If \s appeared in a character class, it removed the VT character from
157        the class, even if it had been included by some previous item, for example
158        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
159        of \s, but is part of the POSIX "space" class.)
161    4.  A partial match never returns an empty string (because you can always
162        match an empty string at the end of the subject); however the checking for
163        an empty string was starting at the "start of match" point. This has been
164        changed to the "earliest inspected character" point, because the returned
165        data for a partial match starts at this character. This means that, for
166        example, /(?<=abc)def/ gives a partial match for the subject "abc"
167        (previously it gave "no match").
169    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
170        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
171        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
172        has an implication that the given string is incomplete (because a partial
173        match is preferred over a full match). For this reason, these items now
174        give a partial match in this situation. [Aside: previously, the one case
175        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
176        match rather than a full match, which was wrong by the old rules, but is
177        now correct.]
179    6.  There was a bug in the handling of #-introduced comments, recognized when
180        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
181        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
182        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
183        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
184        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
185        places in pcre_compile().
187    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
188        comments when looking ahead for named forward references to subpatterns,
189        the only newline sequence it recognized was NL. It now handles newlines
190        according to the set newline convention.
192    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
193        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
194        cater for a lack of strerror(). These oversights have been fixed.
196    9.  Added --match-limit and --recursion-limit to pcregrep.
198    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
200    11. When the -o option was used, pcregrep was setting a return code of 1, even
201        when matches were found, and --line-buffered was not being honoured.
203    12. Added an optional parentheses number to the -o and --only-matching options
204        of pcregrep.
206    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
207        can match an empty string. The code to do it in pcretest and pcredemo
208        needed fixing:
210        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
211            only one byte after an empty string match just before CRLF (this case
212            just got forgotten; "any" and "anycrlf" were OK).
214        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
215            mode when an empty string match preceded an ASCII character followed by
216            a non-ASCII character. (The code for advancing by one character rather
217            than one byte was nonsense.)
219        (c) The pcredemo.c sample program did not have any code at all to handle
220            the cases when CRLF is a valid newline sequence.
222    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
223        as a starting offset was within the subject string. There is now a new
224        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
225        negative or greater than the length of the string. In order to test this,
226        pcretest is extended to allow the setting of negative starting offsets.
228    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
229        starting offset points to the beginning of a UTF-8 character was
230        unnecessarily clumsy. I tidied it up.
232    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
233        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
235    17. Nobody had reported that the --include_dir option, which was added in
236        release 7.7 should have been called --include-dir (hyphen, not underscore)
237        for compatibility with GNU grep. I have changed it to --include-dir, but
238        left --include_dir as an undocumented synonym, and the same for
239        --exclude-dir, though that is not available in GNU grep, at least as of
240        release 2.5.4.
242    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
243        characters from a string of bytes) have been redefined so as not to use
244        loops, in order to improve performance in some environments. At the same
245        time, I abstracted some of the common code into auxiliary macros to save
246        repetition (this should not affect the compiled code).
248    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
249        compile-time error is now given if \c is not followed by an ASCII
250        character, that is, a byte less than 128. (In EBCDIC mode, the code is
251        different, and any byte value is allowed.)
253    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
254        START_OPTIMIZE option, which is now allowed at compile time - but just
255        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
256        to pcregrep and other applications that have no direct access to PCRE
257        options. The new /Y option in pcretest sets this option when calling
258        pcre_compile().
260    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
261        back references. Groups containing recursive back references were forced to
262        be atomic by that change, but in the case of named groups, the amount of
263        memory required was incorrectly computed, leading to "Failed: internal
264        error: code overflow". This has been fixed.
266    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
267        pcretest.c, to avoid build problems in some Borland environments.
270    Version 8.10 25-Jun-2010
271    ------------------------
273    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
274        THEN.
276    2.  (*ACCEPT) was not working when inside an atomic group.
278    3.  Inside a character class, \B is treated as a literal by default, but
279        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
280        causes the error). The code is unchanged, but I tidied the documentation.
282    4.  Inside a character class, PCRE always treated \R and \X as literals,
283        whereas Perl faults them if its -w option is set. I have changed PCRE so
284        that it faults them when PCRE_EXTRA is set.
286    5.  Added support for \N, which always matches any character other than
287        newline. (It is the same as "." when PCRE_DOTALL is not set.)
289    6.  When compiling pcregrep with newer versions of gcc which may have
290        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
291        declared with attribute warn_unused_result" were given. Just casting the
292        result to (void) does not stop the warnings; a more elaborate fudge is
293        needed. I've used a macro to implement this.
295    7.  Minor change to pcretest.c to avoid a compiler warning.
297    8.  Added four artifical Unicode properties to help with an option to make
298        \s etc use properties (see next item). The new properties are: Xan
299        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
301    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
302        use Unicode properties. (*UCP) at the start of a pattern can be used to set
303        this option. Modified pcretest to add /W to test this facility. Added
304        REG_UCP to make it available via the POSIX interface.
306    10. Added --line-buffered to pcregrep.
308    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
309        studied, and the match started with a letter with a code point greater than
310        127 whose first byte was different to the first byte of the other case of
311        the letter, the other case of this starting letter was not recognized
312        (#976).
314    12. If a pattern that was studied started with a repeated Unicode property
315        test, for example, \p{Nd}+, there was the theoretical possibility of
316        setting up an incorrect bitmap of starting bytes, but fortunately it could
317        not have actually happened in practice until change 8 above was made (it
318        added property types that matched character-matching opcodes).
320    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
321        possible starting bytes for non-anchored patterns.
323    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
324        \R, and also a number of cases that involve Unicode properties, both
325        explicit and implicit when PCRE_UCP is set.
327    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
328        input, it could crash or give wrong results if characters with values
329        greater than 0xc0 were present in the subject string. (Detail: it assumed
330        UTF-8 input when processing these items.)
332    16. Added a lot of (int) casts to avoid compiler warnings in systems where
333        size_t is 64-bit (#991).
335    17. Added a check for running out of memory when PCRE is compiled with
336        --disable-stack-for-recursion (#990).
338    18. If the last data line in a file for pcretest does not have a newline on
339        the end, a newline was missing in the output.
341    19. The default pcre_chartables.c file recognizes only ASCII characters (values
342        less than 128) in its various bitmaps. However, there is a facility for
343        generating tables according to the current locale when PCRE is compiled. It
344        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
345        characters, are recognized by isspace() and therefore were getting set in
346        these tables, and indeed these tables seem to approximate to ISO 8859. This
347        caused a problem in UTF-8 mode when pcre_study() was used to create a list
348        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
349        which of course cannot start UTF-8 characters. I have changed the code so
350        that only real ASCII characters (less than 128) and the correct starting
351        bytes for UTF-8 encodings are set for characters greater than 127 when in
352        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
353        altogether.)
355    20. Added the /T option to pcretest so as to be able to run tests with non-
356        standard character tables, thus making it possible to include the tests
357        used for 19 above in the standard set of tests.
359    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
360        reference to a subpattern the other side of a comment that contains an
361        opening parenthesis caused either an internal compiling error, or a
362        reference to the wrong subpattern.
365    Version 8.02 19-Mar-2010
366    ------------------------
368    1.  The Unicode data tables have been updated to Unicode 5.2.0.
370    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
371        configured.
373    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
374        original author of that file, following a query about its status.
376    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
377        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
379    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
380        quantifier applied to a forward-referencing subroutine call, could compile
381        incorrect code or give the error "internal error: previously-checked
382        referenced subpattern not found".
384    6.  Both MS Visual Studio and Symbian OS have problems with initializing
385        variables to point to external functions. For these systems, therefore,
386        pcre_malloc etc. are now initialized to local functions that call the
387        relevant global functions.
389    7.  There were two entries missing in the vectors called coptable and poptable
390        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
391        I've fixed the data, and added a kludgy way of testing at compile time that
392        the lengths are correct (equal to the number of opcodes).
394    8.  Following on from 7, I added a similar kludge to check the length of the
395        eint vector in pcreposix.c.
397    9.  Error texts for pcre_compile() are held as one long string to avoid too
398        much relocation at load time. To find a text, the string is searched,
399        counting zeros. There was no check for running off the end of the string,
400        which could happen if a new error number was added without updating the
401        string.
403    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
405    11. \K was not working if it appeared in an atomic group or in a group that
406        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
407        \K is "not well defined" if used in an assertion. PCRE now accepts it if
408        the assertion is positive, but not if it is negative.
410    12. Change 11 fortuitously reduced the size of the stack frame used in the
411        "match()" function of pcre_exec.c by one pointer. Forthcoming
412        implementation of support for (*MARK) will need an extra pointer on the
413        stack; I have reserved it now, so that the stack frame size does not
414        decrease.
416    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
417        item in branch that calls a recursion is a subroutine call - as in the
418        second branch in the above example - was incorrectly given the compile-
419        time error "recursive call could loop indefinitely" because pcre_compile()
420        was not correctly checking the subroutine for matching a non-empty string.
422    14. The checks for overrunning compiling workspace could trigger after an
423        overrun had occurred. This is a "should never occur" error, but it can be
424        triggered by pathological patterns such as hundreds of nested parentheses.
425        The checks now trigger 100 bytes before the end of the workspace.
427    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
430    Version 8.01 19-Jan-2010
431    ------------------------
433    1.  If a pattern contained a conditional subpattern with only one branch (in
434        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
435        computed the wrong minimum data length (which is of course zero for such
436        subpatterns). This could cause incorrect "no match" results.
438    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
439        the pattern is reset in the first branch, pcre_compile() failed with
440        "internal error: code overflow at offset...". This happened only when
441        the reset was to the original external option setting. (An optimization
442        abstracts leading options settings into an external setting, which was the
443        cause of this.)
445    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
446        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
447        assertion pattern did not match (meaning that the assertion was true), it
448        was incorrectly treated as false if the SKIP had been reached during the
449        matching. This also applied to assertions used as conditions.
451    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
452        assertion subpattern, including such a pattern used as a condition,
453        unpredictable results occurred, instead of the error return
456    5.  The C++ GlobalReplace function was not working like Perl for the special
457        situation when an empty string is matched. It now does the fancy magic
458        stuff that is necessary.
460    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
461        removed. (These were left over from very, very early versions of PCRE.)
463    7.  Some cosmetic changes to the code to make life easier when compiling it
464        as part of something else:
466        (a) Change DEBUG to PCRE_DEBUG.
468        (b) In pcre_compile(), rename the member of the "branch_chain" structure
469            called "current" as "current_branch", to prevent a collision with the
470            Linux macro when compiled as a kernel module.
472        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
473            prevent a collision with the Linux macro when compiled as a kernel
474            module.
476    8.  In pcre_compile() there are some checks for integer overflows that used to
477        cast potentially large values to (double). This has been changed to that
478        when building, a check for int64_t is made, and if it is found, it is used
479        instead, thus avoiding the use of floating point arithmetic. (There is no
480        other use of FP in PCRE.) If int64_t is not found, the fallback is to
481        double.
483    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
484        2005 (difference between two addresses compared to an unsigned value).
486    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
487        custom one, because of the following reported problem in Windows:
489          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
490              under Win32.
491          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
492              therefore missing the function definition.
493          - The compiler thus generates a "C" signature for the test function.
494          - The linker fails to find the "C" function.
495          - PCRE fails to configure if asked to do so against libbz2.
497    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
498        messages were output:
500          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
501          rerunning libtoolize, to keep the correct libtool macros in-tree.
502          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
504        I have done both of these things.
506    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
507        most of the time, it *can* run out if it is given a pattern that contains a
508        runaway infinite recursion. I updated the discussion in the pcrestack man
509        page.
511    13. Now that we have gone to the x.xx style of version numbers, the minor
512        version may start with zero. Using 08 or 09 is a bad idea because users
513        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
514        interpreted as invalid octal numbers. I've updated the previous comment in
515        configure.ac, and also added a check that gives an error if 08 or 09 are
516        used.
518    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
519        causing partial matching to fail when the end of the subject matched \W
520        in a UTF-8 pattern where \W was quantified with a minimum of 3.
522    15. There were some discrepancies between the declarations in pcre_internal.h
523        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
524        their definitions. The declarations used "const uschar *" and the
525        definitions used USPTR. Even though USPTR is normally defined as "const
526        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
527        reported that: "This difference in casting confuses some C++ compilers, for
528        example, SunCC recognizes above declarations as different functions and
529        generates broken code for hbpcre." I have changed the declarations to use
530        USPTR.
532    16. GNU libtool is named differently on some systems. The autogen.sh script now
533        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
534        (FreeBSD).
536    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
537        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
538        comment: "Figure out how to create a longlong from a string: strtoll and
539        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
540        instance, but it only takes 2 args instead of 3!"
542    18. A subtle bug concerned with back references has been fixed by a change of
543        specification, with a corresponding code fix. A pattern such as
544        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
545        refers, was giving matches when it shouldn't. For example, xa=xaaa would
546        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
547        same bug. Such groups have to be quantified to be useful, or contained
548        inside another quantified group. (If there's no repetition, the reference
549        can never match.) The problem arises because, having left the group and
550        moved on to the rest of the pattern, a later failure that backtracks into
551        the group uses the captured value from the final iteration of the group
552        rather than the correct earlier one. I have fixed this in PCRE by forcing
553        any group that contains a reference to itself to be an atomic group; that
554        is, there cannot be any backtracking into it once it has completed. This is
555        similar to recursive and subroutine calls.
558    Version 8.00 19-Oct-09
559    ----------------------
561    1.  The table for translating pcre_compile() error codes into POSIX error codes
562        was out-of-date, and there was no check on the pcre_compile() error code
563        being within the table. This could lead to an OK return being given in
564        error.
566    2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
567        "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
568        in a Windows environment.
570    3.  The pcregrep --count option prints the count for each file even when it is
571        zero, as does GNU grep. However, pcregrep was also printing all files when
572        --files-with-matches was added. Now, when both options are given, it prints
573        counts only for those files that have at least one match. (GNU grep just
574        prints the file name in this circumstance, but including the count seems
575        more useful - otherwise, why use --count?) Also ensured that the
576        combination -clh just lists non-zero counts, with no names.
578    4.  The long form of the pcregrep -F option was incorrectly implemented as
579        --fixed_strings instead of --fixed-strings. This is an incompatible change,
580        but it seems right to fix it, and I didn't think it was worth preserving
581        the old behaviour.
583    5.  The command line items --regex=pattern and --regexp=pattern were not
584        recognized by pcregrep, which required --regex pattern or --regexp pattern
585        (with a space rather than an '='). The man page documented the '=' forms,
586        which are compatible with GNU grep; these now work.
588    6.  No libpcreposix.pc file was created for pkg-config; there was just
589        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
591    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
592        when UCP support is not needed, by modifying the Python script that
593        generates it from Unicode data files. This should not matter if the module
594        is correctly used as a library, but I received one complaint about 50K of
595        unwanted data. My guess is that the person linked everything into his
596        program rather than using a library. Anyway, it does no harm.
598    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
599        was a minimum greater than 1 for a wide character in a possessive
600        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
601        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
602        character. Chaos in the form of incorrect output or a compiling loop could
603        result.
605    9.  The restrictions on what a pattern can contain when partial matching is
606        requested for pcre_exec() have been removed. All patterns can now be
607        partially matched by this function. In addition, if there are at least two
608        slots in the offset vector, the offset of the earliest inspected character
609        for the match and the offset of the end of the subject are set in them when
610        PCRE_ERROR_PARTIAL is returned.
612    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
613        synonymous with PCRE_PARTIAL, for backwards compatibility, and
614        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
615        and may be more useful for multi-segment matching.
617    11. Partial matching with pcre_exec() is now more intuitive. A partial match
618        used to be given if ever the end of the subject was reached; now it is
619        given only if matching could not proceed because another character was
620        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
621        string "Z", which now yields "no match" instead of "partial match". In the
622        case of pcre_dfa_exec(), "no match" is given if every matching path for the
623        final character ended with (*FAIL).
625    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
626        if the pattern had a "must contain" character that was already found in the
627        earlier partial match, unless partial matching was again requested. For
628        example, with the pattern /dog.(body)?/, the "must contain" character is
629        "g". If the first part-match was for the string "dog", restarting with
630        "sbody" failed. This bug has been fixed.
632    13. The string returned by pcre_dfa_exec() after a partial match has been
633        changed so that it starts at the first inspected character rather than the
634        first character of the match. This makes a difference only if the pattern
635        starts with a lookbehind assertion or \b or \B (\K is not supported by
636        pcre_dfa_exec()). It's an incompatible change, but it makes the two
637        matching functions compatible, and I think it's the right thing to do.
639    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
640        so that the demonstration program is easily available in environments where
641        PCRE has not been installed from source.
643    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
644        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
645        library.
647    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
648        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
649        is not the first non-POSIX option to be added. Clearly some people find
650        these options useful.
652    17. If a caller to the POSIX matching function regexec() passes a non-zero
653        value for nmatch with a NULL value for pmatch, the value of
654        nmatch is forced to zero.
656    18. RunGrepTest did not have a test for the availability of the -u option of
657        the diff command, as RunTest does. It now checks in the same way as
658        RunTest, and also checks for the -b option.
660    19. If an odd number of negated classes containing just a single character
661        interposed, within parentheses, between a forward reference to a named
662        subpattern and the definition of the subpattern, compilation crashed with
663        an internal error, complaining that it could not find the referenced
664        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
665        [The bug was that it was starting one character too far in when skipping
666        over the character class, thus treating the ] as data rather than
667        terminating the class. This meant it could skip too much.]
669    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
670        /g option in pcretest when the pattern contains \K, which makes it possible
671        to have an empty string match not at the start, even when the pattern is
672        anchored. Updated pcretest and pcredemo to use this option.
674    21. If the maximum number of capturing subpatterns in a recursion was greater
675        than the maximum at the outer level, the higher number was returned, but
676        with unset values at the outer level. The correct (outer level) value is
677        now given.
679    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
680        PCRE did not set those parentheses (unlike Perl). I have now found a way to
681        make it do so. The string so far is captured, making this feature
682        compatible with Perl.
684    23. The tests have been re-organized, adding tests 11 and 12, to make it
685        possible to check the Perl 5.10 features against Perl 5.10.
687    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
688        pattern matches a fixed length string. PCRE did not allow this; now it
689        does. Neither allows recursion.
691    25. I finally figured out how to implement a request to provide the minimum
692        length of subject string that was needed in order to match a given pattern.
693        (It was back references and recursion that I had previously got hung up
694        on.) This code has now been added to pcre_study(); it finds a lower bound
695        to the length of subject needed. It is not necessarily the greatest lower
696        bound, but using it to avoid searching strings that are too short does give
697        some useful speed-ups. The value is available to calling programs via
698        pcre_fullinfo().
700    26. While implementing 25, I discovered to my embarrassment that pcretest had
701        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
702        study optimizations had never been tested with that matching function.
703        Oops. What is worse, even when it was passed study data, there was a bug in
704        pcre_dfa_exec() that meant it never actually used it. Double oops. There
705        were also very few tests of studied patterns with pcre_dfa_exec().
707    27. If (?| is used to create subpatterns with duplicate numbers, they are now
708        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
709        on the other side of the coin, they are no longer allowed to have different
710        names, because these cannot be distinguished in PCRE, and this has caused
711        confusion. (This is a difference from Perl.)
713    28. When duplicate subpattern names are present (necessarily with different
714        numbers, as required by 27 above), and a test is made by name in a
715        conditional pattern, either for a subpattern having been matched, or for
716        recursion in such a pattern, all the associated numbered subpatterns are
717        tested, and the overall condition is true if the condition is true for any
718        one of them. This is the way Perl works, and is also more like the way
719        testing by number works.
722    Version 7.9 11-Apr-09
723    ---------------------
725    1.  When building with support for bzlib/zlib (pcregrep) and/or readline
726        (pcretest), all targets were linked against these libraries. This included
727        libpcre, libpcreposix, and libpcrecpp, even though they do not use these
728        libraries. This caused unwanted dependencies to be created. This problem
729        has been fixed, and now only pcregrep is linked with bzlib/zlib and only
730        pcretest is linked with readline.
732    2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
733        "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
734        moved outside it again, because FALSE and TRUE are already defined in AIX,
735        but BOOL is not.
737    3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and
738        PCRE_MATCH_LIMIT_RECURSION values as ints, when they should be long ints.
740    4.  The pcregrep documentation said spaces were inserted as well as colons (or
741        hyphens) following file names and line numbers when outputting matching
742        lines. This is not true; no spaces are inserted. I have also clarified the
743        wording for the --colour (or --color) option.
745    5.  In pcregrep, when --colour was used with -o, the list of matching strings
746        was not coloured; this is different to GNU grep, so I have changed it to be
747        the same.
749    6.  When --colo(u)r was used in pcregrep, only the first matching substring in
750        each matching line was coloured. Now it goes on to look for further matches
751        of any of the test patterns, which is the same behaviour as GNU grep.
753    7.  A pattern that could match an empty string could cause pcregrep to loop; it
754        doesn't make sense to accept an empty string match in pcregrep, so I have
755        locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
756        seems to be how GNU grep behaves.
758    8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
759        start or after a newline", because the conditional assertion was not being
760        correctly handled. The rule now is that both the assertion and what follows
761        in the first alternative must satisfy the test.
763    9.  If auto-callout was enabled in a pattern with a conditional group whose
764        condition was an assertion, PCRE could crash during matching, both with
765        pcre_exec() and pcre_dfa_exec().
767    10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was
768        used for matching.
770    11. Unicode property support in character classes was not working for
771        characters (bytes) greater than 127 when not in UTF-8 mode.
773    12. Added the -M command line option to pcretest.
775    14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
777    15. Added the PCRE_NO_START_OPTIMIZE match-time option.
779    16. Added comments and documentation about mis-use of no_arg in the C++
780        wrapper.
782    17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
783        from Martin Jerabek that uses macro names for all relevant character and
784        string constants.
786    18. Added to pcre_internal.h two configuration checks: (a) If both EBCDIC and
787        SUPPORT_UTF8 are set, give an error; (b) If SUPPORT_UCP is set without
788        SUPPORT_UTF8, define SUPPORT_UTF8. The "configure" script handles both of
789        these, but not everybody uses configure.
791    19. A conditional group that had only one branch was not being correctly
792        recognized as an item that could match an empty string. This meant that an
793        enclosing group might also not be so recognized, causing infinite looping
794        (and probably a segfault) for patterns such as ^"((?(?=[a])[^"])|b)*"$
795        with the subject "ab", where knowledge that the repeated group can match
796        nothing is needed in order to break the loop.
798    20. If a pattern that was compiled with callouts was matched using pcre_dfa_
799        exec(), but without supplying a callout function, matching went wrong.
801    21. If PCRE_ERROR_MATCHLIMIT occurred during a recursion, there was a memory
802        leak if the size of the offset vector was greater than 30. When the vector
803        is smaller, the saved offsets during recursion go onto a local stack
804        vector, but for larger vectors malloc() is used. It was failing to free
805        when the recursion yielded PCRE_ERROR_MATCH_LIMIT (or any other "abnormal"
806        error, in fact).
808    22. There was a missing #ifdef SUPPORT_UTF8 round one of the variables in the
809        heapframe that is used only when UTF-8 support is enabled. This caused no
810        problem, but was untidy.
812    23. Steven Van Ingelgem's patch to CMakeLists.txt to change the name
813        CMAKE_BINARY_DIR to PROJECT_BINARY_DIR so that it works when PCRE is
814        included within another project.
816    24. Steven Van Ingelgem's patches to add more options to the CMake support,
817        slightly modified by me:
819          (a) PCRE_BUILD_TESTS can be set OFF not to build the tests, including
820              not building pcregrep.
822          (b) PCRE_BUILD_PCREGREP can be see OFF not to build pcregrep, but only
823              if PCRE_BUILD_TESTS is also set OFF, because the tests use pcregrep.
825    25. Forward references, both numeric and by name, in patterns that made use of
826        duplicate group numbers, could behave incorrectly or give incorrect errors,
827        because when scanning forward to find the reference group, PCRE was not
828        taking into account the duplicate group numbers. A pattern such as
829        ^X(?3)(a)(?|(b)|(q))(Y) is an example.
831    26. Changed a few more instances of "const unsigned char *" to USPTR, making
832        the feature of a custom pointer more persuasive (as requested by a user).
834    27. Wrapped the definitions of fileno and isatty for Windows, which appear in
835        pcretest.c, inside #ifndefs, because it seems they are sometimes already
836        pre-defined.
838    28. Added support for (*UTF8) at the start of a pattern.
840    29. Arrange for flags added by the "release type" setting in CMake to be shown
841        in the configuration summary.
844    Version 7.8 05-Sep-08
845    ---------------------
847    1.  Replaced UCP searching code with optimized version as implemented for Ad
848        Muncher (http://www.admuncher.com/) by Peter Kankowski. This uses a two-
849        stage table and inline lookup instead of a function, giving speed ups of 2
850        to 5 times on some simple patterns that I tested. Permission was given to
851        distribute the MultiStage2.py script that generates the tables (it's not in
852        the tarball, but is in the Subversion repository).
854    2.  Updated the Unicode datatables to Unicode 5.1.0. This adds yet more
855        scripts.
857    3.  Change 12 for 7.7 introduced a bug in pcre_study() when a pattern contained
858        a group with a zero qualifier. The result of the study could be incorrect,
859        or the function might crash, depending on the pattern.
861    4.  Caseless matching was not working for non-ASCII characters in back
862        references. For example, /(\x{de})\1/8i was not matching \x{de}\x{fe}.
863        It now works when Unicode Property Support is available.
865    5.  In pcretest, an escape such as \x{de} in the data was always generating
866        a UTF-8 string, even in non-UTF-8 mode. Now it generates a single byte in
867        non-UTF-8 mode. If the value is greater than 255, it gives a warning about
868        truncation.
870    6.  Minor bugfix in pcrecpp.cc (change "" == ... to NULL == ...).
872    7.  Added two (int) casts to pcregrep when printing the difference of two
873        pointers, in case they are 64-bit values.
875    8.  Added comments about Mac OS X stack usage to the pcrestack man page and to
876        test 2 if it fails.
878    9.  Added PCRE_CALL_CONVENTION just before the names of all exported functions,
879        and a #define of that name to empty if it is not externally set. This is to
880        allow users of MSVC to set it if necessary.
882    10. The PCRE_EXP_DEFN macro which precedes exported functions was missing from
883        the convenience functions in the pcre_get.c source file.
885    11. An option change at the start of a pattern that had top-level alternatives
886        could cause overwriting and/or a crash. This command provoked a crash in
887        some environments:
889          printf "/(?i)[\xc3\xa9\xc3\xbd]|[\xc3\xa9\xc3\xbdA]/8\n" | pcretest
891        This potential security problem was recorded as CVE-2008-2371.
893    12. For a pattern where the match had to start at the beginning or immediately
894        after a newline (e.g /.*anything/ without the DOTALL flag), pcre_exec() and
895        pcre_dfa_exec() could read past the end of the passed subject if there was
896        no match. To help with detecting such bugs (e.g. with valgrind), I modified
897        pcretest so that it places the subject at the end of its malloc-ed buffer.
899    13. The change to pcretest in 12 above threw up a couple more cases when pcre_
900        exec() might read past the end of the data buffer in UTF-8 mode.
902    14. A similar bug to 7.3/2 existed when the PCRE_FIRSTLINE option was set and
903        the data contained the byte 0x85 as part of a UTF-8 character within its
904        first line. This applied both to normal and DFA matching.
906    15. Lazy qualifiers were not working in some cases in UTF-8 mode. For example,
907        /^[^d]*?$/8 failed to match "abc".
909    16. Added a missing copyright notice to pcrecpp_internal.h.
911    17. Make it more clear in the documentation that values returned from
912        pcre_exec() in ovector are byte offsets, not character counts.
914    18. Tidied a few places to stop certain compilers from issuing warnings.
916    19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
917        supplied by Stefan Weber. I made a further small update for 7.8 because
918        there is a change of source arrangements: the pcre_searchfuncs.c module is
919        replaced by pcre_ucd.c.
922    Version 7.7 07-May-08
923    ---------------------
925    1.  Applied Craig's patch to sort out a long long problem: "If we can't convert
926        a string to a long long, pretend we don't even have a long long." This is
927        done by checking for the strtoq, strtoll, and _strtoi64 functions.
929    2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
930        pre-7.6 versions, which defined a global no_arg variable instead of putting
931        it in the RE class. (See also #8 below.)
933    3.  Remove a line of dead code, identified by coverity and reported by Nuno
934        Lopes.
936    4.  Fixed two related pcregrep bugs involving -r with --include or --exclude:
938        (1) The include/exclude patterns were being applied to the whole pathnames
939            of files, instead of just to the final components.
941        (2) If there was more than one level of directory, the subdirectories were
942            skipped unless they satisfied the include/exclude conditions. This is
943            inconsistent with GNU grep (and could even be seen as contrary to the
944            pcregrep specification - which I improved to make it absolutely clear).
945            The action now is always to scan all levels of directory, and just
946            apply the include/exclude patterns to regular files.
948    5.  Added the --include_dir and --exclude_dir patterns to pcregrep, and used
949        --exclude_dir in the tests to avoid scanning .svn directories.
951    6.  Applied Craig's patch to the QuoteMeta function so that it escapes the
952        NUL character as backslash + 0 rather than backslash + NUL, because PCRE
953        doesn't support NULs in patterns.
955    7.  Added some missing "const"s to declarations of static tables in
956        pcre_compile.c and pcre_dfa_exec.c.
958    8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
959        caused by fix #2  above. (Subsequently also a second patch to fix the
960        first patch. And a third patch - this was a messy problem.)
962    9.  Applied Craig's patch to remove the use of push_back().
964    10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
965        matching function regexec().
967    11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n',
968        which, however, unlike Perl's \g{...}, are subroutine calls, not back
969        references. PCRE supports relative numbers with this syntax (I don't think
970        Oniguruma does).
972    12. Previously, a group with a zero repeat such as (...){0} was completely
973        omitted from the compiled regex. However, this means that if the group
974        was called as a subroutine from elsewhere in the pattern, things went wrong
975        (an internal error was given). Such groups are now left in the compiled
976        pattern, with a new opcode that causes them to be skipped at execution
977        time.
979    13. Added the PCRE_JAVASCRIPT_COMPAT option. This makes the following changes
980        to the way PCRE behaves:
982        (a) A lone ] character is dis-allowed (Perl treats it as data).
984        (b) A back reference to an unmatched subpattern matches an empty string
985            (Perl fails the current match path).
987        (c) A data ] in a character class must be notated as \] because if the
988            first data character in a class is ], it defines an empty class. (In
989            Perl it is not possible to have an empty class.) The empty class []
990            never matches; it forces failure and is equivalent to (*FAIL) or (?!).
991            The negative empty class [^] matches any one character, independently
992            of the DOTALL setting.
994    14. A pattern such as /(?2)[]a()b](abc)/ which had a forward reference to a
995        non-existent subpattern following a character class starting with ']' and
996        containing () gave an internal compiling error instead of "reference to
997        non-existent subpattern". Fortunately, when the pattern did exist, the
998        compiled code was correct. (When scanning forwards to check for the
999        existencd of the subpattern, it was treating the data ']' as terminating
1000        the class, so got the count wrong. When actually compiling, the reference
1001        was subsequently set up correctly.)
1003    15. The "always fail" assertion (?!) is optimzed to (*FAIL) by pcre_compile;
1004        it was being rejected as not supported by pcre_dfa_exec(), even though
1005        other assertions are supported. I have made pcre_dfa_exec() support
1006        (*FAIL).
1008    16. The implementation of 13c above involved the invention of a new opcode,
1009        OP_ALLANY, which is like OP_ANY but doesn't check the /s flag. Since /s
1010        cannot be changed at match time, I realized I could make a small
1011        improvement to matching performance by compiling OP_ALLANY instead of
1012        OP_ANY for "." when DOTALL was set, and then removing the runtime tests
1013        on the OP_ANY path.
1015    17. Compiling pcretest on Windows with readline support failed without the
1016        following two fixes: (1) Make the unistd.h include conditional on
1017        HAVE_UNISTD_H; (2) #define isatty and fileno as _isatty and _fileno.
1019    18. Changed CMakeLists.txt and cmake/FindReadline.cmake to arrange for the
1020        ncurses library to be included for pcretest when ReadLine support is
1021        requested, but also to allow for it to be overridden. This patch came from
1022        Daniel Bergström.
1024    19. There was a typo in the file ucpinternal.h where f0_rangeflag was defined
1025        as 0x00f00000 instead of 0x00800000. Luckily, this would not have caused
1026        any errors with the current Unicode tables. Thanks to Peter Kankowski for
1027        spotting this.
1030    Version 7.6 28-Jan-08
1031    ---------------------
1033    1.  A character class containing a very large number of characters with
1034        codepoints greater than 255 (in UTF-8 mode, of course) caused a buffer
1035        overflow.
1037    2.  Patch to cut out the "long long" test in pcrecpp_unittest when
1038        HAVE_LONG_LONG is not defined.
1040    3.  Applied Christian Ehrlicher's patch to update the CMake build files to
1041        bring them up to date and include new features. This patch includes:
1043        - Fixed PH's badly added libz and libbz2 support.
1044        - Fixed a problem with static linking.
1045        - Added pcredemo. [But later removed - see 7 below.]
1046        - Fixed dftables problem and added an option.
1047        - Added a number of HAVE_XXX tests, including HAVE_WINDOWS_H and
1048            HAVE_LONG_LONG.
1049        - Added readline support for pcretest.
1050        - Added an listing of the option settings after cmake has run.
1052    4.  A user submitted a patch to Makefile that makes it easy to create
1053        "pcre.dll" under mingw when using Configure/Make. I added stuff to
1054        Makefile.am that cause it to include this special target, without
1055        affecting anything else. Note that the same mingw target plus all
1056        the other distribution libraries and programs are now supported
1057        when configuring with CMake (see 6 below) instead of with
1058        Configure/Make.
1060    5.  Applied Craig's patch that moves no_arg into the RE class in the C++ code.
1061        This is an attempt to solve the reported problem "pcrecpp::no_arg is not
1062        exported in the Windows port". It has not yet been confirmed that the patch
1063        solves the problem, but it does no harm.
1065    6.  Applied Sheri's patch to CMakeLists.txt to add NON_STANDARD_LIB_PREFIX and
1066        NON_STANDARD_LIB_SUFFIX for dll names built with mingw when configured
1067        with CMake, and also correct the comment about stack recursion.
1069    7.  Remove the automatic building of pcredemo from the ./configure system and
1070        from CMakeLists.txt. The whole idea of pcredemo.c is that it is an example
1071        of a program that users should build themselves after PCRE is installed, so
1072        building it automatically is not really right. What is more, it gave
1073        trouble in some build environments.
1075    8.  Further tidies to CMakeLists.txt from Sheri and Christian.
1078    Version 7.5 10-Jan-08
1079  ---------------------  ---------------------
1081  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'  1.  Applied a patch from Craig: "This patch makes it possible to 'ignore'
1082      values in parens when parsing an RE using the C++ wrapper."      values in parens when parsing an RE using the C++ wrapper."
1084  2.  Negative specials like \S did not work in character classes in UTF-8 mode.  2.  Negative specials like \S did not work in character classes in UTF-8 mode.
1085      Characters greater than 255 were excluded from the class instead of being      Characters greater than 255 were excluded from the class instead of being
1086      included.      included.
1088  3.  The same bug as (2) above applied to negated POSIX classes such as  3.  The same bug as (2) above applied to negated POSIX classes such as
1089      [:^space:].      [:^space:].
1091  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it  4.  PCRECPP_STATIC was referenced in pcrecpp_internal.h, but nowhere was it
1092      defined or documented. It seems to have been a typo for PCRE_STATIC, so      defined or documented. It seems to have been a typo for PCRE_STATIC, so
1093      I have changed it.      I have changed it.
1095  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the  5.  The construct (?&) was not diagnosed as a syntax error (it referenced the
1096      first named subpattern) and a construct such as (?&a) would reference the      first named subpattern) and a construct such as (?&a) would reference the
1097      first named subpattern whose name started with "a" (in other words, the      first named subpattern whose name started with "a" (in other words, the
1098      length check was missing). Both these problems are fixed. "Subpattern name      length check was missing). Both these problems are fixed. "Subpattern name
1099      expected" is now given for (?&) (a zero-length name), and this patch also      expected" is now given for (?&) (a zero-length name), and this patch also
1100      makes it give the same error for \k'' (previously it complained that that      makes it give the same error for \k'' (previously it complained that that
1101      was a reference to a non-existent subpattern).      was a reference to a non-existent subpattern).
1103  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;  6.  The erroneous patterns (?+-a) and (?-+a) give different error messages;
1104      this is right because (?- can be followed by option settings as well as by      this is right because (?- can be followed by option settings as well as by
1105      digits. I have, however, made the messages clearer.      digits. I have, however, made the messages clearer.
1107  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns  7.  Patterns such as (?(1)a|b) (a pattern that contains fewer subpatterns
1108      than the number used in the conditional) now cause a compile-time error.      than the number used in the conditional) now cause a compile-time error.
1109      This is actually not compatible with Perl, which accepts such patterns, but      This is actually not compatible with Perl, which accepts such patterns, but
1110      treats the conditional as always being FALSE (as PCRE used to), but it      treats the conditional as always being FALSE (as PCRE used to), but it
1111      seems to me that giving a diagnostic is better.      seems to me that giving a diagnostic is better.
1113  8.  Change "alphameric" to the more common word "alphanumeric" in comments  8.  Change "alphameric" to the more common word "alphanumeric" in comments
1114      and messages.      and messages.
1116  9.  Fix two occurrences of "backslash" in comments that should have been  9.  Fix two occurrences of "backslash" in comments that should have been
1117      "backspace".      "backspace".
1119  10. Remove two redundant lines of code that can never be obeyed (their function  10. Remove two redundant lines of code that can never be obeyed (their function
1120      was moved elsewhere).      was moved elsewhere).
1122  11. The program that makes PCRE's Unicode character property table had a bug  11. The program that makes PCRE's Unicode character property table had a bug
1123      which caused it to generate incorrect table entries for sequences of      which caused it to generate incorrect table entries for sequences of
1124      characters that have the same character type, but are in different scripts.      characters that have the same character type, but are in different scripts.
1125      It amalgamated them into a single range, with the script of the first of      It amalgamated them into a single range, with the script of the first of
1126      them. In other words, some characters were in the wrong script. There were      them. In other words, some characters were in the wrong script. There were
1127      thirteen such cases, affecting characters in the following ranges:      thirteen such cases, affecting characters in the following ranges:
1129        U+002b0 - U+002c1        U+002b0 - U+002c1
1130        U+0060c - U+0060d        U+0060c - U+0060d
1131        U+0061e - U+00612        U+0061e - U+00612
1132        U+0064b - U+0065e        U+0064b - U+0065e
1133        U+0074d - U+0076d        U+0074d - U+0076d
1134        U+01800 - U+01805        U+01800 - U+01805
# Line 65  Version 7.5 12-Nov-07 Line 1139  Version 7.5 12-Nov-07
1139        U+03260 - U+0327f        U+03260 - U+0327f
1140        U+0fb46 - U+0fbb1        U+0fb46 - U+0fbb1
1141        U+10450 - U+1049d        U+10450 - U+1049d
1143  12. The -o option (show only the matching part of a line) for pcregrep was not  12. The -o option (show only the matching part of a line) for pcregrep was not
1144      compatible with GNU grep in that, if there was more than one match in a      compatible with GNU grep in that, if there was more than one match in a
1145      line, it showed only the first of them. It now behaves in the same way as      line, it showed only the first of them. It now behaves in the same way as
1146      GNU grep.      GNU grep.
1148  13. If the -o and -v options were combined for pcregrep, it printed a blank  13. If the -o and -v options were combined for pcregrep, it printed a blank
1149      line for every non-matching line. GNU grep prints nothing, and pcregrep now      line for every non-matching line. GNU grep prints nothing, and pcregrep now
1150      does the same. The return code can be used to tell if there were any      does the same. The return code can be used to tell if there were any
1151      non-matching lines.      non-matching lines.
1153  14. The pattern (?=something)(?R) was not being diagnosed as a potentially  14. Added --file-offsets and --line-offsets to pcregrep.
1155    15. The pattern (?=something)(?R) was not being diagnosed as a potentially
1156      infinitely looping recursion. The bug was that positive lookaheads were not      infinitely looping recursion. The bug was that positive lookaheads were not
1157      being skipped when checking for a possible empty match (negative lookaheads      being skipped when checking for a possible empty match (negative lookaheads
1158      and both kinds of lookbehind were skipped).      and both kinds of lookbehind were skipped).
1160    16. Fixed two typos in the Windows-only code in pcregrep.c, and moved the
1161        inclusion of <windows.h> to before rather than after the definition of
1162        INVALID_FILE_ATTRIBUTES (patch from David Byron).
1164    17. Specifying a possessive quantifier with a specific limit for a Unicode
1165        character property caused pcre_compile() to compile bad code, which led at
1166        runtime to PCRE_ERROR_INTERNAL (-14). Examples of patterns that caused this
1167        are: /\p{Zl}{2,3}+/8 and /\p{Cc}{2}+/8. It was the possessive "+" that
1168        caused the error; without that there was no problem.
1170    18. Added --enable-pcregrep-libz and --enable-pcregrep-libbz2.
1172    19. Added --enable-pcretest-libreadline.
1174    20. In pcrecpp.cc, the variable 'count' was incremented twice in
1175        RE::GlobalReplace(). As a result, the number of replacements returned was
1176        double what it should be. I removed one of the increments, but Craig sent a
1177        later patch that removed the other one (the right fix) and added unit tests
1178        that check the return values (which was not done before).
1180    21. Several CMake things:
1182        (1) Arranged that, when cmake is used on Unix, the libraries end up with
1183            the names libpcre and libpcreposix, not just pcre and pcreposix.
1185        (2) The above change means that pcretest and pcregrep are now correctly
1186            linked with the newly-built libraries, not previously installed ones.
1190    22. In UTF-8 mode, with newline set to "any", a pattern such as .*a.*=.b.*
1191        crashed when matching a string such as a\x{2029}b (note that \x{2029} is a
1192        UTF-8 newline character). The key issue is that the pattern starts .*;
1193        this means that the match must be either at the beginning, or after a
1194        newline. The bug was in the code for advancing after a failed match and
1195        checking that the new position followed a newline. It was not taking
1196        account of UTF-8 characters correctly.
1198    23. PCRE was behaving differently from Perl in the way it recognized POSIX
1199        character classes. PCRE was not treating the sequence [:...:] as a
1200        character class unless the ... were all letters. Perl, however, seems to
1201        allow any characters between [: and :], though of course it rejects as
1202        unknown any "names" that contain non-letters, because all the known class
1203        names consist only of letters. Thus, Perl gives an error for [[:1234:]],
1204        for example, whereas PCRE did not - it did not recognize a POSIX character
1205        class. This seemed a bit dangerous, so the code has been changed to be
1206        closer to Perl. The behaviour is not identical to Perl, because PCRE will
1207        diagnose an unknown class for, for example, [[:l\ower:]] where Perl will
1208        treat it as [[:lower:]]. However, PCRE does now give "unknown" errors where
1209        Perl does, and where it didn't before.
1211    24. Rewrite so as to remove the single use of %n from pcregrep because in some
1212        Windows environments %n is disabled by default.
1215  Version 7.4 21-Sep-07  Version 7.4 21-Sep-07

Removed from v.282  
changed lines
  Added in v.611

  ViewVC Help
Powered by ViewVC 1.1.5