ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 483 by ph10, Mon Jan 4 16:19:17 2010 UTC revision 657 by ph10, Mon Aug 15 17:39:09 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 11-Dec-09  Version 8.13 02-Aug-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, now 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 now
111        *disables* studying, thereby overriding the use of -s on the command line
112        (see 14 above). This is necessary for one or two tests to keep the output
113        identical in both cases.
115    21. When (*ACCEPT) was used in an assertion that matched an empty string and
116        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
118    22. When an atomic group that contained a capturing parenthesis was
119        successfully matched, but the branch in which it appeared failed, the
120        capturing was not being forgotten if a higher numbered group was later
121        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
122        group 1 to "a", when in fact it should be unset. This applied to multi-
123        branched capturing and non-capturing groups, repeated or not, and also to
124        positive assertions (capturing in negative assertions does not happen
125        in PCRE) and also to nested atomic groups.
127    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
128        subject after a captured substring, to make it easier to tell which of a
129        number of identical substrings has been captured.
131    24. The way atomic groups are processed by pcre_exec() has been changed so that
132        if they are repeated, backtracking one repetition now resets captured
133        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
134        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
135        "aaa". Previously, it would have been "a". As part of this code
136        refactoring, the way recursive calls are handled has also been changed.
138    25. If an assertion condition captured any substrings, they were not passed
139        back unless some other capturing happened later. For example, if
140        (?(?=(a))a) was matched against "a", no capturing was returned.
142    26. When studying a pattern that contained subroutine calls or assertions,
143        the code for finding the minimum length of a possible match was handling
144        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
145        group 1 called group 2 while simultaneously a separate group 2 called group
146        1). A stack overflow occurred in this case. I have fixed this by limiting
147        the recursion depth to 10.
149    27. Updated RunTest.bat in the distribution to the version supplied by Tom
150        Fortmann. This supports explicit test numbers on the command line, and has
151        argument validation and error reporting.
153    28. An instance of \X with an unlimited repeat could fail if at any point the
154        first character it looked at was a mark character.
156    29. Some minor code refactoring concerning Unicode properties and scripts
157        should reduce the stack requirement of match() slightly.
159    30. Added the '=' option to pcretest to check the setting of unused capturing
160        slots at the end of the pattern, which are documented as being -1, but are
161        not included in the return count.
163    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
164        compiled something random. Now it gives a compile-time error (as does
165        Perl).
167    32. A *MARK encountered during the processing of a positive assertion is now
168        recorded and passed back (compatible with Perl).
170    33. If --only-matching or --colour was set on a pcregrep call whose pattern
171        had alternative anchored branches, the search for a second match in a line
172        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
173        matched the line "0102" twice. The same bug affected patterns that started
174        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
175        twice.
177    34. Previously, PCRE did not allow quantification of assertions. However, Perl
178        does, and because of capturing effects, quantifying parenthesized
179        assertions may at times be useful. Quantifiers are now allowed for
180        parenthesized assertions.
182    35. A minor code tidy in pcre_compile() when checking options for \R usage.
184    36. \g was being checked for fancy things in a character class, when it should
185        just be a literal "g".
187    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
188        appearance of a nested POSIX class supersedes an apparent external class.
189        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
190        unescaped square brackets may also appear as part of class names. For
191        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
192        more like Perl.
194    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
195        was because it thought it was \N{name}, which is not supported).
197    39. Add minix to OS list not supporting the -S option in pcretest.
199    40. PCRE tries to detect cases of infinite recursion at compile time, but it
200        cannot analyze patterns in sufficient detail to catch mutual recursions
201        such as ((?1))((?2)). There is now a runtime test that gives an error if a
202        subgroup is called recursively as a subpattern for a second time at the
203        same position in the subject string. In previous releases this might have
204        been caught by the recursion limit, or it might have run out of stack.
206    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
207        happen only once. PCRE was, however incorrectly giving a compile time error
208        "recursive call could loop indefinitely" because it cannot analyze the
209        pattern in sufficient detail. The compile time test no longer happens when
210        PCRE is compiling a conditional subpattern, but actual runaway loops are
211        now caught at runtime (see 40 above).
213    42. It seems that Perl allows any characters other than a closing parenthesis
214        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
215        has been changed to be the same.
217    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
218        as not to get warnings when autogen.sh is called. Also changed
219        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
221    44. To help people who use pcregrep to scan files containing exceedingly long
222        lines, the following changes have been made:
224        (a) The default value of the buffer size parameter has been increased from
225            8K to 20K. (The actual buffer used is three times this size.)
227        (b) The default can be changed by ./configure --with-pcregrep-bufsiz when
228            PCRE is built.
230        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
231            to be set at run time.
233        (d) Numerical values in pcregrep options can be followed by K or M, for
234            example --buffer-size=50K.
236        (e) If a line being scanned overflows pcregrep's buffer, an error is now
237            given and the return code is set to 2.
239    45. Add a pointer to the latest mark to the callout data block.
241    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
242        partial match of an empty string instead of no match. This was specific to
243        the use of ".".
245    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
246        complete match instead of a partial match. This bug was dependent on both
247        the PCRE_UTF8 and PCRE_DOTALL options being set.
249    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
250        starting byte set, because \b was not being ignored.
253    Version 8.12 15-Jan-2011
254    ------------------------
256    1.  Fixed some typos in the markup of the man pages, and wrote a script that
257        checks for such things as part of the documentation building process.
259    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
260        --match-limit and --recursion-limit options (added for 8.11). In
261        particular, this made one of the standard tests fail. (The integer value
262        went into the wrong half of a long int.)
264    3.  If the --colour option was given to pcregrep with -v (invert match), it
265        did strange things, either producing crazy output, or crashing. It should,
266        of course, ignore a request for colour when reporting lines that do not
267        match.
269    4.  Another pcregrep bug caused similar problems if --colour was specified with
270        -M (multiline) and the pattern match finished with a line ending.
272    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
273        matched in multiline mode, the following line was shown as part of the
274        match. This seems wrong, so I have changed it.
276    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
277        the check for further matches in the same line (so they could be coloured)
278        to overrun the end of the current line. If another match was found, it was
279        incorrectly shown (and then shown again when found in the next line).
281    7.  If pcregrep was compiled under Windows, there was a reference to the
282        function pcregrep_exit() before it was defined. I am assuming this was
283        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
284        reported by a user. I've moved the definition above the reference.
287    Version 8.11 10-Dec-2010
288    ------------------------
290    1.  (*THEN) was not working properly if there were untried alternatives prior
291        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
292        backtracked to try for "b" instead of moving to the next alternative branch
293        at the same level (in this case, to look for "c"). The Perl documentation
294        is clear that when (*THEN) is backtracked onto, it goes to the "next
295        alternative in the innermost enclosing group".
297    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
298        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
299        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
300        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
301        (*THEN).
303    3.  If \s appeared in a character class, it removed the VT character from
304        the class, even if it had been included by some previous item, for example
305        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
306        of \s, but is part of the POSIX "space" class.)
308    4.  A partial match never returns an empty string (because you can always
309        match an empty string at the end of the subject); however the checking for
310        an empty string was starting at the "start of match" point. This has been
311        changed to the "earliest inspected character" point, because the returned
312        data for a partial match starts at this character. This means that, for
313        example, /(?<=abc)def/ gives a partial match for the subject "abc"
314        (previously it gave "no match").
316    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
317        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
318        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
319        has an implication that the given string is incomplete (because a partial
320        match is preferred over a full match). For this reason, these items now
321        give a partial match in this situation. [Aside: previously, the one case
322        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
323        match rather than a full match, which was wrong by the old rules, but is
324        now correct.]
326    6.  There was a bug in the handling of #-introduced comments, recognized when
327        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
328        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
329        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
330        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
331        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
332        places in pcre_compile().
334    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
335        comments when looking ahead for named forward references to subpatterns,
336        the only newline sequence it recognized was NL. It now handles newlines
337        according to the set newline convention.
339    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
340        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
341        cater for a lack of strerror(). These oversights have been fixed.
343    9.  Added --match-limit and --recursion-limit to pcregrep.
345    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
347    11. When the -o option was used, pcregrep was setting a return code of 1, even
348        when matches were found, and --line-buffered was not being honoured.
350    12. Added an optional parentheses number to the -o and --only-matching options
351        of pcregrep.
353    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
354        can match an empty string. The code to do it in pcretest and pcredemo
355        needed fixing:
357        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
358            only one byte after an empty string match just before CRLF (this case
359            just got forgotten; "any" and "anycrlf" were OK).
361        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
362            mode when an empty string match preceded an ASCII character followed by
363            a non-ASCII character. (The code for advancing by one character rather
364            than one byte was nonsense.)
366        (c) The pcredemo.c sample program did not have any code at all to handle
367            the cases when CRLF is a valid newline sequence.
369    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
370        as a starting offset was within the subject string. There is now a new
371        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
372        negative or greater than the length of the string. In order to test this,
373        pcretest is extended to allow the setting of negative starting offsets.
375    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
376        starting offset points to the beginning of a UTF-8 character was
377        unnecessarily clumsy. I tidied it up.
379    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
380        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
382    17. Nobody had reported that the --include_dir option, which was added in
383        release 7.7 should have been called --include-dir (hyphen, not underscore)
384        for compatibility with GNU grep. I have changed it to --include-dir, but
385        left --include_dir as an undocumented synonym, and the same for
386        --exclude-dir, though that is not available in GNU grep, at least as of
387        release 2.5.4.
389    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
390        characters from a string of bytes) have been redefined so as not to use
391        loops, in order to improve performance in some environments. At the same
392        time, I abstracted some of the common code into auxiliary macros to save
393        repetition (this should not affect the compiled code).
395    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
396        compile-time error is now given if \c is not followed by an ASCII
397        character, that is, a byte less than 128. (In EBCDIC mode, the code is
398        different, and any byte value is allowed.)
400    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
401        START_OPTIMIZE option, which is now allowed at compile time - but just
402        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
403        to pcregrep and other applications that have no direct access to PCRE
404        options. The new /Y option in pcretest sets this option when calling
405        pcre_compile().
407    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
408        back references. Groups containing recursive back references were forced to
409        be atomic by that change, but in the case of named groups, the amount of
410        memory required was incorrectly computed, leading to "Failed: internal
411        error: code overflow". This has been fixed.
413    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
414        pcretest.c, to avoid build problems in some Borland environments.
417    Version 8.10 25-Jun-2010
418    ------------------------
420    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
421        THEN.
423    2.  (*ACCEPT) was not working when inside an atomic group.
425    3.  Inside a character class, \B is treated as a literal by default, but
426        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
427        causes the error). The code is unchanged, but I tidied the documentation.
429    4.  Inside a character class, PCRE always treated \R and \X as literals,
430        whereas Perl faults them if its -w option is set. I have changed PCRE so
431        that it faults them when PCRE_EXTRA is set.
433    5.  Added support for \N, which always matches any character other than
434        newline. (It is the same as "." when PCRE_DOTALL is not set.)
436    6.  When compiling pcregrep with newer versions of gcc which may have
437        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
438        declared with attribute warn_unused_result" were given. Just casting the
439        result to (void) does not stop the warnings; a more elaborate fudge is
440        needed. I've used a macro to implement this.
442    7.  Minor change to pcretest.c to avoid a compiler warning.
444    8.  Added four artifical Unicode properties to help with an option to make
445        \s etc use properties (see next item). The new properties are: Xan
446        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
448    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
449        use Unicode properties. (*UCP) at the start of a pattern can be used to set
450        this option. Modified pcretest to add /W to test this facility. Added
451        REG_UCP to make it available via the POSIX interface.
453    10. Added --line-buffered to pcregrep.
455    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
456        studied, and the match started with a letter with a code point greater than
457        127 whose first byte was different to the first byte of the other case of
458        the letter, the other case of this starting letter was not recognized
459        (#976).
461    12. If a pattern that was studied started with a repeated Unicode property
462        test, for example, \p{Nd}+, there was the theoretical possibility of
463        setting up an incorrect bitmap of starting bytes, but fortunately it could
464        not have actually happened in practice until change 8 above was made (it
465        added property types that matched character-matching opcodes).
467    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
468        possible starting bytes for non-anchored patterns.
470    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
471        \R, and also a number of cases that involve Unicode properties, both
472        explicit and implicit when PCRE_UCP is set.
474    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
475        input, it could crash or give wrong results if characters with values
476        greater than 0xc0 were present in the subject string. (Detail: it assumed
477        UTF-8 input when processing these items.)
479    16. Added a lot of (int) casts to avoid compiler warnings in systems where
480        size_t is 64-bit (#991).
482    17. Added a check for running out of memory when PCRE is compiled with
483        --disable-stack-for-recursion (#990).
485    18. If the last data line in a file for pcretest does not have a newline on
486        the end, a newline was missing in the output.
488    19. The default pcre_chartables.c file recognizes only ASCII characters (values
489        less than 128) in its various bitmaps. However, there is a facility for
490        generating tables according to the current locale when PCRE is compiled. It
491        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
492        characters, are recognized by isspace() and therefore were getting set in
493        these tables, and indeed these tables seem to approximate to ISO 8859. This
494        caused a problem in UTF-8 mode when pcre_study() was used to create a list
495        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
496        which of course cannot start UTF-8 characters. I have changed the code so
497        that only real ASCII characters (less than 128) and the correct starting
498        bytes for UTF-8 encodings are set for characters greater than 127 when in
499        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
500        altogether.)
502    20. Added the /T option to pcretest so as to be able to run tests with non-
503        standard character tables, thus making it possible to include the tests
504        used for 19 above in the standard set of tests.
506    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
507        reference to a subpattern the other side of a comment that contains an
508        opening parenthesis caused either an internal compiling error, or a
509        reference to the wrong subpattern.
512    Version 8.02 19-Mar-2010
513    ------------------------
515    1.  The Unicode data tables have been updated to Unicode 5.2.0.
517    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
518        configured.
520    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
521        original author of that file, following a query about its status.
523    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
524        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
526    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
527        quantifier applied to a forward-referencing subroutine call, could compile
528        incorrect code or give the error "internal error: previously-checked
529        referenced subpattern not found".
531    6.  Both MS Visual Studio and Symbian OS have problems with initializing
532        variables to point to external functions. For these systems, therefore,
533        pcre_malloc etc. are now initialized to local functions that call the
534        relevant global functions.
536    7.  There were two entries missing in the vectors called coptable and poptable
537        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
538        I've fixed the data, and added a kludgy way of testing at compile time that
539        the lengths are correct (equal to the number of opcodes).
541    8.  Following on from 7, I added a similar kludge to check the length of the
542        eint vector in pcreposix.c.
544    9.  Error texts for pcre_compile() are held as one long string to avoid too
545        much relocation at load time. To find a text, the string is searched,
546        counting zeros. There was no check for running off the end of the string,
547        which could happen if a new error number was added without updating the
548        string.
550    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
552    11. \K was not working if it appeared in an atomic group or in a group that
553        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
554        \K is "not well defined" if used in an assertion. PCRE now accepts it if
555        the assertion is positive, but not if it is negative.
557    12. Change 11 fortuitously reduced the size of the stack frame used in the
558        "match()" function of pcre_exec.c by one pointer. Forthcoming
559        implementation of support for (*MARK) will need an extra pointer on the
560        stack; I have reserved it now, so that the stack frame size does not
561        decrease.
563    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
564        item in branch that calls a recursion is a subroutine call - as in the
565        second branch in the above example - was incorrectly given the compile-
566        time error "recursive call could loop indefinitely" because pcre_compile()
567        was not correctly checking the subroutine for matching a non-empty string.
569    14. The checks for overrunning compiling workspace could trigger after an
570        overrun had occurred. This is a "should never occur" error, but it can be
571        triggered by pathological patterns such as hundreds of nested parentheses.
572        The checks now trigger 100 bytes before the end of the workspace.
574    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
577    Version 8.01 19-Jan-2010
578    ------------------------
580  1.  If a pattern contained a conditional subpattern with only one branch (in  1.  If a pattern contained a conditional subpattern with only one branch (in
581      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
582      computed the wrong minimum data length (which is of course zero for such      computed the wrong minimum data length (which is of course zero for such
583      subpatterns).      subpatterns). This could cause incorrect "no match" results.
585  2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of  2.  For patterns such as (?i)a(?-i)b|c where an option setting at the start of
586      the pattern is reset in the first branch, pcre_compile() failed with      the pattern is reset in the first branch, pcre_compile() failed with
# Line 61  Version 8.01 11-Dec-09 Line 634  Version 8.01 11-Dec-09
634      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
636        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
637          under Win32.            under Win32.
638        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
639          therefore missing the function definition.            therefore missing the function definition.
640        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
641        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
642        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
644  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these  11. When running libtoolize from libtool-2.2.6b as part of autogen.sh, these
645      messages were output:      messages were output:
647        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and        Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
648        rerunning libtoolize, to keep the correct libtool macros in-tree.        rerunning libtoolize, to keep the correct libtool macros in-tree.
649        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.        Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
651      I have done both of these things.      I have done both of these things.
653  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()  12. Although pcre_dfa_exec() does not use nearly as much stack as pcre_exec()
654      most of the time, it *can* run out if it is given a pattern that contains a      most of the time, it *can* run out if it is given a pattern that contains a
655      runaway infinite recursion. I updated the discussion in the pcrestack man      runaway infinite recursion. I updated the discussion in the pcrestack man
656      page.      page.
658  13. Now that we have gone to the x.xx style of version numbers, the minor  13. Now that we have gone to the x.xx style of version numbers, the minor
659      version may start with zero. Using 08 or 09 is a bad idea because users      version may start with zero. Using 08 or 09 is a bad idea because users
660      might check the value of PCRE_MINOR in their code, and 08 or 09 may be      might check the value of PCRE_MINOR in their code, and 08 or 09 may be
661      interpreted as invalid octal numbers. I've updated the previous comment in      interpreted as invalid octal numbers. I've updated the previous comment in
662      configure.ac, and also added a check that gives an error if 08 or 09 are      configure.ac, and also added a check that gives an error if 08 or 09 are
663      used.      used.
665  14. Change 8.00/11 was not quite complete: code had been accidentally omitted,  14. Change 8.00/11 was not quite complete: code had been accidentally omitted,
666      causing partial matching to fail when the end of the subject matched \W      causing partial matching to fail when the end of the subject matched \W
667      in a UTF-8 pattern where \W was quantified with a minimum of 3.      in a UTF-8 pattern where \W was quantified with a minimum of 3.
669  15. There were some discrepancies between the declarations in pcre_internal.h  15. There were some discrepancies between the declarations in pcre_internal.h
670      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and      of _pcre_is_newline(), _pcre_was_newline(), and _pcre_valid_utf8() and
671      their definitions. The declarations used "const uschar *" and the      their definitions. The declarations used "const uschar *" and the
672      definitions used USPTR. Even though USPTR is normally defined as "const      definitions used USPTR. Even though USPTR is normally defined as "const
673      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was      unsigned char *" (and uschar is typedeffed as "unsigned char"), it was
674      reported that: "This difference in casting confuses some C++ compilers, for      reported that: "This difference in casting confuses some C++ compilers, for
675      example, SunCC recognizes above declarations as different functions and      example, SunCC recognizes above declarations as different functions and
676      generates broken code for hbpcre." I have changed the declarations to use      generates broken code for hbpcre." I have changed the declarations to use
677      USPTR.      USPTR.
679    16. GNU libtool is named differently on some systems. The autogen.sh script now
680        tries several variants such as glibtoolize (MacOSX) and libtoolize1x
681        (FreeBSD).
683    17. Applied Craig's patch that fixes an HP aCC compile error in pcre 8.00
684        (strtoXX undefined when compiling pcrecpp.cc). The patch contains this
685        comment: "Figure out how to create a longlong from a string: strtoll and
686        equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
687        instance, but it only takes 2 args instead of 3!"
689    18. A subtle bug concerned with back references has been fixed by a change of
690        specification, with a corresponding code fix. A pattern such as
691        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
692        refers, was giving matches when it shouldn't. For example, xa=xaaa would
693        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
694        same bug. Such groups have to be quantified to be useful, or contained
695        inside another quantified group. (If there's no repetition, the reference
696        can never match.) The problem arises because, having left the group and
697        moved on to the rest of the pattern, a later failure that backtracks into
698        the group uses the captured value from the final iteration of the group
699        rather than the correct earlier one. I have fixed this in PCRE by forcing
700        any group that contains a reference to itself to be an atomic group; that
701        is, there cannot be any backtracking into it once it has completed. This is
702        similar to recursive and subroutine calls.
705  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09

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

  ViewVC Help
Powered by ViewVC 1.1.5