ViewVC logotype

Diff of /code/trunk/ChangeLog

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

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

Removed from v.423  
changed lines
  Added in v.594

  ViewVC Help
Powered by ViewVC 1.1.5