ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 419 by ph10, Wed Aug 12 10:45:33 2009 UTC revision 608 by ph10, Sun Jun 12 16:25:55 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.00 ??-???-??  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.
95    Version 8.12 15-Jan-2011
96    ------------------------
98    1.  Fixed some typos in the markup of the man pages, and wrote a script that
99        checks for such things as part of the documentation building process.
101    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
102        --match-limit and --recursion-limit options (added for 8.11). In
103        particular, this made one of the standard tests fail. (The integer value
104        went into the wrong half of a long int.)
106    3.  If the --colour option was given to pcregrep with -v (invert match), it
107        did strange things, either producing crazy output, or crashing. It should,
108        of course, ignore a request for colour when reporting lines that do not
109        match.
111    4.  Another pcregrep bug caused similar problems if --colour was specified with
112        -M (multiline) and the pattern match finished with a line ending.
114    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
115        matched in multiline mode, the following line was shown as part of the
116        match. This seems wrong, so I have changed it.
118    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
119        the check for further matches in the same line (so they could be coloured)
120        to overrun the end of the current line. If another match was found, it was
121        incorrectly shown (and then shown again when found in the next line).
123    7.  If pcregrep was compiled under Windows, there was a reference to the
124        function pcregrep_exit() before it was defined. I am assuming this was
125        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
126        reported by a user. I've moved the definition above the reference.
129    Version 8.11 10-Dec-2010
130    ------------------------
132    1.  (*THEN) was not working properly if there were untried alternatives prior
133        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
134        backtracked to try for "b" instead of moving to the next alternative branch
135        at the same level (in this case, to look for "c"). The Perl documentation
136        is clear that when (*THEN) is backtracked onto, it goes to the "next
137        alternative in the innermost enclosing group".
139    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
140        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
141        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
142        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
143        (*THEN).
145    3.  If \s appeared in a character class, it removed the VT character from
146        the class, even if it had been included by some previous item, for example
147        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
148        of \s, but is part of the POSIX "space" class.)
150    4.  A partial match never returns an empty string (because you can always
151        match an empty string at the end of the subject); however the checking for
152        an empty string was starting at the "start of match" point. This has been
153        changed to the "earliest inspected character" point, because the returned
154        data for a partial match starts at this character. This means that, for
155        example, /(?<=abc)def/ gives a partial match for the subject "abc"
156        (previously it gave "no match").
158    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
159        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
160        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
161        has an implication that the given string is incomplete (because a partial
162        match is preferred over a full match). For this reason, these items now
163        give a partial match in this situation. [Aside: previously, the one case
164        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
165        match rather than a full match, which was wrong by the old rules, but is
166        now correct.]
168    6.  There was a bug in the handling of #-introduced comments, recognized when
169        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
170        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
171        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
172        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
173        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
174        places in pcre_compile().
176    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
177        comments when looking ahead for named forward references to subpatterns,
178        the only newline sequence it recognized was NL. It now handles newlines
179        according to the set newline convention.
181    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
182        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
183        cater for a lack of strerror(). These oversights have been fixed.
185    9.  Added --match-limit and --recursion-limit to pcregrep.
187    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
189    11. When the -o option was used, pcregrep was setting a return code of 1, even
190        when matches were found, and --line-buffered was not being honoured.
192    12. Added an optional parentheses number to the -o and --only-matching options
193        of pcregrep.
195    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
196        can match an empty string. The code to do it in pcretest and pcredemo
197        needed fixing:
199        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
200            only one byte after an empty string match just before CRLF (this case
201            just got forgotten; "any" and "anycrlf" were OK).
203        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
204            mode when an empty string match preceded an ASCII character followed by
205            a non-ASCII character. (The code for advancing by one character rather
206            than one byte was nonsense.)
208        (c) The pcredemo.c sample program did not have any code at all to handle
209            the cases when CRLF is a valid newline sequence.
211    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
212        as a starting offset was within the subject string. There is now a new
213        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
214        negative or greater than the length of the string. In order to test this,
215        pcretest is extended to allow the setting of negative starting offsets.
217    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
218        starting offset points to the beginning of a UTF-8 character was
219        unnecessarily clumsy. I tidied it up.
221    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
222        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
224    17. Nobody had reported that the --include_dir option, which was added in
225        release 7.7 should have been called --include-dir (hyphen, not underscore)
226        for compatibility with GNU grep. I have changed it to --include-dir, but
227        left --include_dir as an undocumented synonym, and the same for
228        --exclude-dir, though that is not available in GNU grep, at least as of
229        release 2.5.4.
231    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
232        characters from a string of bytes) have been redefined so as not to use
233        loops, in order to improve performance in some environments. At the same
234        time, I abstracted some of the common code into auxiliary macros to save
235        repetition (this should not affect the compiled code).
237    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
238        compile-time error is now given if \c is not followed by an ASCII
239        character, that is, a byte less than 128. (In EBCDIC mode, the code is
240        different, and any byte value is allowed.)
242    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
243        START_OPTIMIZE option, which is now allowed at compile time - but just
244        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
245        to pcregrep and other applications that have no direct access to PCRE
246        options. The new /Y option in pcretest sets this option when calling
247        pcre_compile().
249    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
250        back references. Groups containing recursive back references were forced to
251        be atomic by that change, but in the case of named groups, the amount of
252        memory required was incorrectly computed, leading to "Failed: internal
253        error: code overflow". This has been fixed.
255    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
256        pcretest.c, to avoid build problems in some Borland environments.
259    Version 8.10 25-Jun-2010
260    ------------------------
262    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
263        THEN.
265    2.  (*ACCEPT) was not working when inside an atomic group.
267    3.  Inside a character class, \B is treated as a literal by default, but
268        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
269        causes the error). The code is unchanged, but I tidied the documentation.
271    4.  Inside a character class, PCRE always treated \R and \X as literals,
272        whereas Perl faults them if its -w option is set. I have changed PCRE so
273        that it faults them when PCRE_EXTRA is set.
275    5.  Added support for \N, which always matches any character other than
276        newline. (It is the same as "." when PCRE_DOTALL is not set.)
278    6.  When compiling pcregrep with newer versions of gcc which may have
279        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
280        declared with attribute warn_unused_result" were given. Just casting the
281        result to (void) does not stop the warnings; a more elaborate fudge is
282        needed. I've used a macro to implement this.
284    7.  Minor change to pcretest.c to avoid a compiler warning.
286    8.  Added four artifical Unicode properties to help with an option to make
287        \s etc use properties (see next item). The new properties are: Xan
288        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
290    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
291        use Unicode properties. (*UCP) at the start of a pattern can be used to set
292        this option. Modified pcretest to add /W to test this facility. Added
293        REG_UCP to make it available via the POSIX interface.
295    10. Added --line-buffered to pcregrep.
297    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
298        studied, and the match started with a letter with a code point greater than
299        127 whose first byte was different to the first byte of the other case of
300        the letter, the other case of this starting letter was not recognized
301        (#976).
303    12. If a pattern that was studied started with a repeated Unicode property
304        test, for example, \p{Nd}+, there was the theoretical possibility of
305        setting up an incorrect bitmap of starting bytes, but fortunately it could
306        not have actually happened in practice until change 8 above was made (it
307        added property types that matched character-matching opcodes).
309    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
310        possible starting bytes for non-anchored patterns.
312    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
313        \R, and also a number of cases that involve Unicode properties, both
314        explicit and implicit when PCRE_UCP is set.
316    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
317        input, it could crash or give wrong results if characters with values
318        greater than 0xc0 were present in the subject string. (Detail: it assumed
319        UTF-8 input when processing these items.)
321    16. Added a lot of (int) casts to avoid compiler warnings in systems where
322        size_t is 64-bit (#991).
324    17. Added a check for running out of memory when PCRE is compiled with
325        --disable-stack-for-recursion (#990).
327    18. If the last data line in a file for pcretest does not have a newline on
328        the end, a newline was missing in the output.
330    19. The default pcre_chartables.c file recognizes only ASCII characters (values
331        less than 128) in its various bitmaps. However, there is a facility for
332        generating tables according to the current locale when PCRE is compiled. It
333        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
334        characters, are recognized by isspace() and therefore were getting set in
335        these tables, and indeed these tables seem to approximate to ISO 8859. This
336        caused a problem in UTF-8 mode when pcre_study() was used to create a list
337        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
338        which of course cannot start UTF-8 characters. I have changed the code so
339        that only real ASCII characters (less than 128) and the correct starting
340        bytes for UTF-8 encodings are set for characters greater than 127 when in
341        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
342        altogether.)
344    20. Added the /T option to pcretest so as to be able to run tests with non-
345        standard character tables, thus making it possible to include the tests
346        used for 19 above in the standard set of tests.
348    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
349        reference to a subpattern the other side of a comment that contains an
350        opening parenthesis caused either an internal compiling error, or a
351        reference to the wrong subpattern.
354    Version 8.02 19-Mar-2010
355    ------------------------
357    1.  The Unicode data tables have been updated to Unicode 5.2.0.
359    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
360        configured.
362    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
363        original author of that file, following a query about its status.
365    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
366        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
368    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
369        quantifier applied to a forward-referencing subroutine call, could compile
370        incorrect code or give the error "internal error: previously-checked
371        referenced subpattern not found".
373    6.  Both MS Visual Studio and Symbian OS have problems with initializing
374        variables to point to external functions. For these systems, therefore,
375        pcre_malloc etc. are now initialized to local functions that call the
376        relevant global functions.
378    7.  There were two entries missing in the vectors called coptable and poptable
379        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
380        I've fixed the data, and added a kludgy way of testing at compile time that
381        the lengths are correct (equal to the number of opcodes).
383    8.  Following on from 7, I added a similar kludge to check the length of the
384        eint vector in pcreposix.c.
386    9.  Error texts for pcre_compile() are held as one long string to avoid too
387        much relocation at load time. To find a text, the string is searched,
388        counting zeros. There was no check for running off the end of the string,
389        which could happen if a new error number was added without updating the
390        string.
392    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
394    11. \K was not working if it appeared in an atomic group or in a group that
395        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
396        \K is "not well defined" if used in an assertion. PCRE now accepts it if
397        the assertion is positive, but not if it is negative.
399    12. Change 11 fortuitously reduced the size of the stack frame used in the
400        "match()" function of pcre_exec.c by one pointer. Forthcoming
401        implementation of support for (*MARK) will need an extra pointer on the
402        stack; I have reserved it now, so that the stack frame size does not
403        decrease.
405    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
406        item in branch that calls a recursion is a subroutine call - as in the
407        second branch in the above example - was incorrectly given the compile-
408        time error "recursive call could loop indefinitely" because pcre_compile()
409        was not correctly checking the subroutine for matching a non-empty string.
411    14. The checks for overrunning compiling workspace could trigger after an
412        overrun had occurred. This is a "should never occur" error, but it can be
413        triggered by pathological patterns such as hundreds of nested parentheses.
414        The checks now trigger 100 bytes before the end of the workspace.
416    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
419    Version 8.01 19-Jan-2010
420    ------------------------
422    1.  If a pattern contained a conditional subpattern with only one branch (in
423        particular, this includes all (*DEFINE) patterns), a call to pcre_study()
424        computed the wrong minimum data length (which is of course zero for such
425        subpatterns). This could cause incorrect "no match" results.
427    2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
428        the pattern is reset in the first branch, pcre_compile() failed with
429        "internal error: code overflow at offset...". This happened only when
430        the reset was to the original external option setting. (An optimization
431        abstracts leading options settings into an external setting, which was the
432        cause of this.)
434    3.  A pattern such as ^(?!a(*SKIP)b) where a negative assertion contained one
435        of the verbs SKIP, PRUNE, or COMMIT, did not work correctly. When the
436        assertion pattern did not match (meaning that the assertion was true), it
437        was incorrectly treated as false if the SKIP had been reached during the
438        matching. This also applied to assertions used as conditions.
440    4.  If an item that is not supported by pcre_dfa_exec() was encountered in an
441        assertion subpattern, including such a pattern used as a condition,
442        unpredictable results occurred, instead of the error return
445    5.  The C++ GlobalReplace function was not working like Perl for the special
446        situation when an empty string is matched. It now does the fancy magic
447        stuff that is necessary.
449    6.  In pcre_internal.h, obsolete includes to setjmp.h and stdarg.h have been
450        removed. (These were left over from very, very early versions of PCRE.)
452    7.  Some cosmetic changes to the code to make life easier when compiling it
453        as part of something else:
455        (a) Change DEBUG to PCRE_DEBUG.
457        (b) In pcre_compile(), rename the member of the "branch_chain" structure
458            called "current" as "current_branch", to prevent a collision with the
459            Linux macro when compiled as a kernel module.
461        (c) In pcre_study(), rename the function set_bit() as set_table_bit(), to
462            prevent a collision with the Linux macro when compiled as a kernel
463            module.
465    8.  In pcre_compile() there are some checks for integer overflows that used to
466        cast potentially large values to (double). This has been changed to that
467        when building, a check for int64_t is made, and if it is found, it is used
468        instead, thus avoiding the use of floating point arithmetic. (There is no
469        other use of FP in PCRE.) If int64_t is not found, the fallback is to
470        double.
472    9.  Added two casts to avoid signed/unsigned warnings from VS Studio Express
473        2005 (difference between two addresses compared to an unsigned value).
475    10. Change the standard AC_CHECK_LIB test for libbz2 in configure.ac to a
476        custom one, because of the following reported problem in Windows:
478          - libbz2 uses the Pascal calling convention (WINAPI) for the functions
479              under Win32.
480          - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
481              therefore missing the function definition.
482          - The compiler thus generates a "C" signature for the test function.
483          - The linker fails to find the "C" function.
484          - PCRE fails to configure if asked to do so against libbz2.
486    11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
487        messages were output:
489          Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
490          rerunning libtoolize, to keep the correct libtool macros in-tree.
491          Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
493        I have done both of these things.
495    12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
496        most of the time, it *can* run out if it is given a pattern that contains a
497        runaway infinite recursion. I updated the discussion in the pcrestack man
498        page.
500    13. Now that we have gone to the x.xx style of version numbers, the minor
501        version may start with zero. Using 08 or 09 is a bad idea because users
502        might check the value of PCRE_MINOR in their code, and 08 or 09 may be
503        interpreted as invalid octal numbers. I've updated the previous comment in
504        configure.ac, and also added a check that gives an error if 08 or 09 are
505        used.
507    14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
508        causing partial matching to fail when the end of the subject matched \W
509        in a UTF-8 pattern where \W was quantified with a minimum of 3.
511    15. There were some discrepancies between the declarations in pcre_internal.h
512        of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
513        their definitions. The declarations used "const uschar *" and the
514        definitions used USPTR. Even though USPTR is normally defined as "const
515        unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
516        reported that: "This difference in casting confuses some C++ compilers, for
517        example, SunCC recognizes above declarations as different functions and
518        generates broken code for hbpcre." I have changed the declarations to use
519        USPTR.
521    16. GNU libtool is named differently on some systems. The autogen.sh script now
522        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
523        (FreeBSD).
525    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
526        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
527        comment: "Figure out how to create a longlong from a string: strtoll and
528        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
529        instance, but it only takes 2 args instead of 3!"
531    18. A subtle bug concerned with back references has been fixed by a change of
532        specification, with a corresponding code fix. A pattern such as
533        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
534        refers, was giving matches when it shouldn't. For example, xa=xaaa would
535        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
536        same bug. Such groups have to be quantified to be useful, or contained
537        inside another quantified group. (If there's no repetition, the reference
538        can never match.) The problem arises because, having left the group and
539        moved on to the rest of the pattern, a later failure that backtracks into
540        the group uses the captured value from the final iteration of the group
541        rather than the correct earlier one. I have fixed this in PCRE by forcing
542        any group that contains a reference to itself to be an atomic group; that
543        is, there cannot be any backtracking into it once it has completed. This is
544        similar to recursive and subroutine calls.
547    Version 8.00 19-Oct-09
548  ----------------------  ----------------------
550  1.  The table for translating pcre_compile() error codes into POSIX error codes  1.  The table for translating pcre_compile() error codes into POSIX error codes
551      was out-of-date, and there was no check on the pcre_compile() error code      was out-of-date, and there was no check on the pcre_compile() error code
552      being within the table. This could lead to an OK return being given in      being within the table. This could lead to an OK return being given in
553      error.      error.
555  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,  2.  Changed the call to open a subject file in pcregrep from fopen(pathname,
556      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests      "r") to fopen(pathname, "rb"), which fixed a problem with some of the tests
557      in a Windows environment.      in a Windows environment.
559    3.  The pcregrep --count option prints the count for each file even when it is
560        zero, as does GNU grep. However, pcregrep was also printing all files when
561        --files-with-matches was added. Now, when both options are given, it prints
562        counts only for those files that have at least one match. (GNU grep just
563        prints the file name in this circumstance, but including the count seems
564        more useful - otherwise, why use --count?) Also ensured that the
565        combination -clh just lists non-zero counts, with no names.
567    4.  The long form of the pcregrep -F option was incorrectly implemented as
568        --fixed_strings instead of --fixed-strings. This is an incompatible change,
569        but it seems right to fix it, and I didn't think it was worth preserving
570        the old behaviour.
572    5.  The command line items --regex=pattern and --regexp=pattern were not
573        recognized by pcregrep, which required --regex pattern or --regexp pattern
574        (with a space rather than an '='). The man page documented the '=' forms,
575        which are compatible with GNU grep; these now work.
577    6.  No libpcreposix.pc file was created for pkg-config; there was just
578        libpcre.pc and libpcrecpp.pc. The omission has been rectified.
580    7.  Added #ifndef SUPPORT_UCP into the pcre_ucd.c module, to reduce its size
581        when UCP support is not needed, by modifying the Python script that
582        generates it from Unicode data files. This should not matter if the module
583        is correctly used as a library, but I received one complaint about 50K of
584        unwanted data. My guess is that the person linked everything into his
585        program rather than using a library. Anyway, it does no harm.
587    8.  A pattern such as /\x{123}{2,2}+/8 was incorrectly compiled; the trigger
588        was a minimum greater than 1 for a wide character in a possessive
589        repetition. The same bug could also affect patterns like /(\x{ff}{0,2})*/8
590        which had an unlimited repeat of a nested, fixed maximum repeat of a wide
591        character. Chaos in the form of incorrect output or a compiling loop could
592        result.
594    9.  The restrictions on what a pattern can contain when partial matching is
595        requested for pcre_exec() have been removed. All patterns can now be
596        partially matched by this function. In addition, if there are at least two
597        slots in the offset vector, the offset of the earliest inspected character
598        for the match and the offset of the end of the subject are set in them when
599        PCRE_ERROR_PARTIAL is returned.
601    10. Partial matching has been split into two forms: PCRE_PARTIAL_SOFT, which is
602        synonymous with PCRE_PARTIAL, for backwards compatibility, and
603        PCRE_PARTIAL_HARD, which causes a partial match to supersede a full match,
604        and may be more useful for multi-segment matching.
606    11. Partial matching with pcre_exec() is now more intuitive. A partial match
607        used to be given if ever the end of the subject was reached; now it is
608        given only if matching could not proceed because another character was
609        needed. This makes a difference in some odd cases such as Z(*FAIL) with the
610        string "Z", which now yields "no match" instead of "partial match". In the
611        case of pcre_dfa_exec(), "no match" is given if every matching path for the
612        final character ended with (*FAIL).
614    12. Restarting a match using pcre_dfa_exec() after a partial match did not work
615        if the pattern had a "must contain" character that was already found in the
616        earlier partial match, unless partial matching was again requested. For
617        example, with the pattern /dog.(body)?/, the "must contain" character is
618        "g". If the first part-match was for the string "dog", restarting with
619        "sbody" failed. This bug has been fixed.
621    13. The string returned by pcre_dfa_exec() after a partial match has been
622        changed so that it starts at the first inspected character rather than the
623        first character of the match. This makes a difference only if the pattern
624        starts with a lookbehind assertion or \b or \B (\K is not supported by
625        pcre_dfa_exec()). It's an incompatible change, but it makes the two
626        matching functions compatible, and I think it's the right thing to do.
628    14. Added a pcredemo man page, created automatically from the pcredemo.c file,
629        so that the demonstration program is easily available in environments where
630        PCRE has not been installed from source.
632    15. Arranged to add -DPCRE_STATIC to cflags in libpcre.pc, libpcreposix.cp,
633        libpcrecpp.pc and pcre-config when PCRE is not compiled as a shared
634        library.
636    16. Added REG_UNGREEDY to the pcreposix interface, at the request of a user.
637        It maps to PCRE_UNGREEDY. It is not, of course, POSIX-compatible, but it
638        is not the first non-POSIX option to be added. Clearly some people find
639        these options useful.
641    17. If a caller to the POSIX matching function regexec() passes a non-zero
642        value for nmatch with a NULL value for pmatch, the value of
643        nmatch is forced to zero.
645    18. RunGrepTest did not have a test for the availability of the -u option of
646        the diff command, as RunTest does. It now checks in the same way as
647        RunTest, and also checks for the -b option.
649    19. If an odd number of negated classes containing just a single character
650        interposed, within parentheses, between a forward reference to a named
651        subpattern and the definition of the subpattern, compilation crashed with
652        an internal error, complaining that it could not find the referenced
653        subpattern. An example of a crashing pattern is /(?&A)(([^m])(?<A>))/.
654        [The bug was that it was starting one character too far in when skipping
655        over the character class, thus treating the ] as data rather than
656        terminating the class. This meant it could skip too much.]
658    20. Added PCRE_NOTEMPTY_ATSTART in order to be able to correctly implement the
659        /g option in pcretest when the pattern contains \K, which makes it possible
660        to have an empty string match not at the start, even when the pattern is
661        anchored. Updated pcretest and pcredemo to use this option.
663    21. If the maximum number of capturing subpatterns in a recursion was greater
664        than the maximum at the outer level, the higher number was returned, but
665        with unset values at the outer level. The correct (outer level) value is
666        now given.
668    22. If (*ACCEPT) appeared inside capturing parentheses, previous releases of
669        PCRE did not set those parentheses (unlike Perl). I have now found a way to
670        make it do so. The string so far is captured, making this feature
671        compatible with Perl.
673    23. The tests have been re-organized, adding tests 11 and 12, to make it
674        possible to check the Perl 5.10 features against Perl 5.10.
676    24. Perl 5.10 allows subroutine calls in lookbehinds, as long as the subroutine
677        pattern matches a fixed length string. PCRE did not allow this; now it
678        does. Neither allows recursion.
680    25. I finally figured out how to implement a request to provide the minimum
681        length of subject string that was needed in order to match a given pattern.
682        (It was back references and recursion that I had previously got hung up
683        on.) This code has now been added to pcre_study(); it finds a lower bound
684        to the length of subject needed. It is not necessarily the greatest lower
685        bound, but using it to avoid searching strings that are too short does give
686        some useful speed-ups. The value is available to calling programs via
687        pcre_fullinfo().
689    26. While implementing 25, I discovered to my embarrassment that pcretest had
690        not been passing the result of pcre_study() to pcre_dfa_exec(), so the
691        study optimizations had never been tested with that matching function.
692        Oops. What is worse, even when it was passed study data, there was a bug in
693        pcre_dfa_exec() that meant it never actually used it. Double oops. There
694        were also very few tests of studied patterns with pcre_dfa_exec().
696    27. If (?| is used to create subpatterns with duplicate numbers, they are now
697        allowed to have the same name, even if PCRE_DUPNAMES is not set. However,
698        on the other side of the coin, they are no longer allowed to have different
699        names, because these cannot be distinguished in PCRE, and this has caused
700        confusion. (This is a difference from Perl.)
702    28. When duplicate subpattern names are present (necessarily with different
703        numbers, as required by 27 above), and a test is made by name in a
704        conditional pattern, either for a subpattern having been matched, or for
705        recursion in such a pattern, all the associated numbered subpatterns are
706        tested, and the overall condition is true if the condition is true for any
707        one of them. This is the way Perl works, and is also more like the way
708        testing by number works.
711  Version 7.9 11-Apr-09  Version 7.9 11-Apr-09

Removed from v.419  
changed lines
  Added in v.608

  ViewVC Help
Powered by ViewVC 1.1.5