ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.248  
changed lines
  Added in v.616

  ViewVC Help
Powered by ViewVC 1.1.5