ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 486 by ph10, Tue Jan 5 17:44:57 2010 UTC revision 701 by ph10, Tue Sep 20 11:30:56 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.01 06-Jan-10  Version 8.20 12-Sep-2011
5  ----------------------  ------------------------
7    1.  Change 37 of 8.13 broke patterns like [:a]...[b:] because it thought it had
8        a POSIX class. After further experiments with Perl, which convinced me that
9        Perl has bugs and confusions, a closing square bracket is no longer allowed
10        in a POSIX name. This bug also affected patterns with classes that started
11        with full stops.
13    2.  If a pattern such as /(a)b|ac/ is matched against "ac", there is no
14        captured substring, but while checking the failing first alternative,
15        substring 1 is temporarily captured. If the output vector supplied to
16        pcre_exec() was not big enough for this capture, the yield of the function
17        was still zero ("insufficient space for captured substrings"). This cannot
18        be totally fixed without adding another stack variable, which seems a lot
19        of expense for a edge case. However, I have improved the situation in cases
20        such as /(a)(b)x|abc/ matched against "abc", where the return code
21        indicates that fewer than the maximum number of slots in the ovector have
22        been set.
24    3.  Related to (2) above: when there are more back references in a pattern than
25        slots in the output vector, pcre_exec() uses temporary memory during
26        matching, and copies in the captures as far as possible afterwards. It was
27        using the entire output vector, but this conflicts with the specification
28        that only 2/3 is used for passing back captured substrings. Now it uses
29        only the first 2/3, for compatibility. This is, of course, another edge
30        case.
32    4.  Zoltan Herczeg's just-in-time compiler support has been integrated into the
33        main code base, and can be used by building with --enable-jit. When this is
34        done, pcregrep automatically uses it unless --disable-pcregrep-jit or the
35        runtime --no-jit option is given.
37    5.  When the number of matches in a pcre_dfa_exec() run exactly filled the
38        ovector, the return from the function was zero, implying that there were
39        other matches that did not fit. The correct "exactly full" value is now
40        returned.
42    6.  If a subpattern that was called recursively or as a subroutine contained
43        (*PRUNE) or any other control that caused it to give a non-standard return,
44        invalid errors such as "Error -26 (nested recursion at the same subject
45        position)" or even infinite loops could occur.
47    7.  If a pattern such as /a(*SKIP)c|b(*ACCEPT)|/ was studied, it stopped
48        computing the minimum length on reaching *ACCEPT, and so ended up with the
49        wrong value of 1 rather than 0. Further investigation indicates that
50        computing a minimum subject length in the presence of *ACCEPT is difficult
51        (think back references, subroutine calls), and so I have changed the code
52        so that no minimum is registered for a pattern that contains *ACCEPT.
54    8.  If (*THEN) was present in the first (true) branch of a conditional group,
55        it was not handled as intended.
57    9.  Replaced RunTest.bat with the much improved version provided by Sheri
58        Pierce.
60    10. A pathological pattern such as /(*ACCEPT)a/ was miscompiled, thinking that
61        the first byte in a match must be "a".
64    Version 8.13 16-Aug-2011
65    ------------------------
67    1.  The Unicode data tables have been updated to Unicode 6.0.0.
69    2.  Two minor typos in pcre_internal.h have been fixed.
71    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
72        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
73        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
75    4.  There were a number of related bugs in the code for matching backrefences
76        caselessly in UTF-8 mode when codes for the characters concerned were
77        different numbers of bytes. For example, U+023A and U+2C65 are an upper
78        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
79        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
80        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
81        2-byte code at the end of the subject (it thought there wasn't enough data
82        left).
84    5.  Comprehensive information about what went wrong is now returned by
85        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
86        as the output vector has at least 2 elements. The offset of the start of
87        the failing character and a reason code are placed in the vector.
89    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
90        now returned is for the first byte of the failing character, instead of the
91        last byte inspected. This is an incompatible change, but I hope it is small
92        enough not to be a problem. It makes the returned offset consistent with
93        pcre_exec() and pcre_dfa_exec().
95    7.  pcretest now gives a text phrase as well as the error number when
96        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
97        failure, the offset and reason code are output.
99    8.  When \R was used with a maximizing quantifier it failed to skip backwards
100        over a \r\n pair if the subsequent match failed. Instead, it just skipped
101        back over a single character (\n). This seems wrong (because it treated the
102        two characters as a single entity when going forwards), conflicts with the
103        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
104        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
105        has been changed.
107    9.  Some internal refactoring has changed the processing so that the handling
108        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
109        time (the PCRE_DOTALL option was changed this way some time ago: version
110        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
111        which was always a bit of a fudge. It also means that there is one less
112        argument for the match() function, which reduces its stack requirements
113        slightly. This change also fixes an incompatibility with Perl: the pattern
114        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
116    10. More internal refactoring has drastically reduced the number of recursive
117        calls to match() for possessively repeated groups such as (abc)++ when
118        using pcre_exec().
120    11. While implementing 10, a number of bugs in the handling of groups were
121        discovered and fixed:
123        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
124        (a|)*(?1) gave a compile-time internal error.
125        ((a|)+)+  did not notice that the outer group could match an empty string.
126        (^a|^)+   was not marked as anchored.
127        (.*a|.*)+ was not marked as matching at start or after a newline.
129    12. Yet more internal refactoring has removed another argument from the match()
130        function. Special calls to this function are now indicated by setting a
131        value in a variable in the "match data" data block.
133    13. Be more explicit in pcre_study() instead of relying on "default" for
134        opcodes that mean there is no starting character; this means that when new
135        ones are added and accidentally left out of pcre_study(), testing should
136        pick them up.
138    14. The -s option of pcretest has been documented for ages as being an old
139        synonym of -m (show memory usage). I have changed it to mean "force study
140        for every regex", that is, assume /S for every regex. This is similar to -i
141        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
142        using it. It makes it easier to run collections of tests with and without
143        study enabled, and thereby test pcre_study() more easily. All the standard
144        tests are now run with and without -s (but some patterns can be marked as
145        "never study" - see 20 below).
147    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
148        restoration of the capturing data to the outer values was not happening
149        correctly.
151    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
152        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
153        pattern had matched an empty string, and so incorrectly returned a no
154        match.
156    17. There was optimizing code for the last branch of non-capturing parentheses,
157        and also for the obeyed branch of a conditional subexpression, which used
158        tail recursion to cut down on stack usage. Unfortunately, now that there is
159        the possibility of (*THEN) occurring in these branches, tail recursion is
160        no longer possible because the return has to be checked for (*THEN). These
161        two optimizations have therefore been removed.
163    18. If a pattern containing \R was studied, it was assumed that \R always
164        matched two bytes, thus causing the minimum subject length to be
165        incorrectly computed because \R can also match just one byte.
167    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
168        was incorrectly computed.
170    20. If /S is present twice on a test pattern in pcretest input, it now
171        *disables* studying, thereby overriding the use of -s on the command line
172        (see 14 above). This is necessary for one or two tests to keep the output
173        identical in both cases.
175    21. When (*ACCEPT) was used in an assertion that matched an empty string and
176        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
178    22. When an atomic group that contained a capturing parenthesis was
179        successfully matched, but the branch in which it appeared failed, the
180        capturing was not being forgotten if a higher numbered group was later
181        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
182        group 1 to "a", when in fact it should be unset. This applied to multi-
183        branched capturing and non-capturing groups, repeated or not, and also to
184        positive assertions (capturing in negative assertions does not happen
185        in PCRE) and also to nested atomic groups.
187    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
188        subject after a captured substring, to make it easier to tell which of a
189        number of identical substrings has been captured.
191    24. The way atomic groups are processed by pcre_exec() has been changed so that
192        if they are repeated, backtracking one repetition now resets captured
193        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
194        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
195        "aaa". Previously, it would have been "a". As part of this code
196        refactoring, the way recursive calls are handled has also been changed.
198    25. If an assertion condition captured any substrings, they were not passed
199        back unless some other capturing happened later. For example, if
200        (?(?=(a))a) was matched against "a", no capturing was returned.
202    26. When studying a pattern that contained subroutine calls or assertions,
203        the code for finding the minimum length of a possible match was handling
204        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
205        group 1 called group 2 while simultaneously a separate group 2 called group
206        1). A stack overflow occurred in this case. I have fixed this by limiting
207        the recursion depth to 10.
209    27. Updated RunTest.bat in the distribution to the version supplied by Tom
210        Fortmann. This supports explicit test numbers on the command line, and has
211        argument validation and error reporting.
213    28. An instance of \X with an unlimited repeat could fail if at any point the
214        first character it looked at was a mark character.
216    29. Some minor code refactoring concerning Unicode properties and scripts
217        should reduce the stack requirement of match() slightly.
219    30. Added the '=' option to pcretest to check the setting of unused capturing
220        slots at the end of the pattern, which are documented as being -1, but are
221        not included in the return count.
223    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
224        compiled something random. Now it gives a compile-time error (as does
225        Perl).
227    32. A *MARK encountered during the processing of a positive assertion is now
228        recorded and passed back (compatible with Perl).
230    33. If --only-matching or --colour was set on a pcregrep call whose pattern
231        had alternative anchored branches, the search for a second match in a line
232        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
233        matched the line "0102" twice. The same bug affected patterns that started
234        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
235        twice.
237    34. Previously, PCRE did not allow quantification of assertions. However, Perl
238        does, and because of capturing effects, quantifying parenthesized
239        assertions may at times be useful. Quantifiers are now allowed for
240        parenthesized assertions.
242    35. A minor code tidy in pcre_compile() when checking options for \R usage.
244    36. \g was being checked for fancy things in a character class, when it should
245        just be a literal "g".
247    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
248        appearance of a nested POSIX class supersedes an apparent external class.
249        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
250        unescaped square brackets may also appear as part of class names. For
251        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
252        more like Perl. (But see 8.20/1 above.)
254    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
255        was because it thought it was \N{name}, which is not supported).
257    39. Add minix to OS list not supporting the -S option in pcretest.
259    40. PCRE tries to detect cases of infinite recursion at compile time, but it
260        cannot analyze patterns in sufficient detail to catch mutual recursions
261        such as ((?1))((?2)). There is now a runtime test that gives an error if a
262        subgroup is called recursively as a subpattern for a second time at the
263        same position in the subject string. In previous releases this might have
264        been caught by the recursion limit, or it might have run out of stack.
266    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
267        happen only once. PCRE was, however incorrectly giving a compile time error
268        "recursive call could loop indefinitely" because it cannot analyze the
269        pattern in sufficient detail. The compile time test no longer happens when
270        PCRE is compiling a conditional subpattern, but actual runaway loops are
271        now caught at runtime (see 40 above).
273    42. It seems that Perl allows any characters other than a closing parenthesis
274        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
275        has been changed to be the same.
277    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
278        as not to get warnings when autogen.sh is called. Also changed
279        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
281    44. To help people who use pcregrep to scan files containing exceedingly long
282        lines, the following changes have been made:
284        (a) The default value of the buffer size parameter has been increased from
285            8K to 20K. (The actual buffer used is three times this size.)
287        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
288            PCRE is built.
290        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
291            to be set at run time.
293        (d) Numerical values in pcregrep options can be followed by K or M, for
294            example --buffer-size=50K.
296        (e) If a line being scanned overflows pcregrep's buffer, an error is now
297            given and the return code is set to 2.
299    45. Add a pointer to the latest mark to the callout data block.
301    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
302        partial match of an empty string instead of no match. This was specific to
303        the use of ".".
305    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
306        complete match instead of a partial match. This bug was dependent on both
307        the PCRE_UTF8 and PCRE_DOTALL options being set.
309    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
310        starting byte set, because \b was not being ignored.
313    Version 8.12 15-Jan-2011
314    ------------------------
316    1.  Fixed some typos in the markup of the man pages, and wrote a script that
317        checks for such things as part of the documentation building process.
319    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
320        --match-limit and --recursion-limit options (added for 8.11). In
321        particular, this made one of the standard tests fail. (The integer value
322        went into the wrong half of a long int.)
324    3.  If the --colour option was given to pcregrep with -v (invert match), it
325        did strange things, either producing crazy output, or crashing. It should,
326        of course, ignore a request for colour when reporting lines that do not
327        match.
329    4.  Another pcregrep bug caused similar problems if --colour was specified with
330        -M (multiline) and the pattern match finished with a line ending.
332    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
333        matched in multiline mode, the following line was shown as part of the
334        match. This seems wrong, so I have changed it.
336    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
337        the check for further matches in the same line (so they could be coloured)
338        to overrun the end of the current line. If another match was found, it was
339        incorrectly shown (and then shown again when found in the next line).
341    7.  If pcregrep was compiled under Windows, there was a reference to the
342        function pcregrep_exit() before it was defined. I am assuming this was
343        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
344        reported by a user. I've moved the definition above the reference.
347    Version 8.11 10-Dec-2010
348    ------------------------
350    1.  (*THEN) was not working properly if there were untried alternatives prior
351        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
352        backtracked to try for "b" instead of moving to the next alternative branch
353        at the same level (in this case, to look for "c"). The Perl documentation
354        is clear that when (*THEN) is backtracked onto, it goes to the "next
355        alternative in the innermost enclosing group".
357    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
358        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
359        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
360        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
361        (*THEN).
363    3.  If \s appeared in a character class, it removed the VT character from
364        the class, even if it had been included by some previous item, for example
365        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
366        of \s, but is part of the POSIX "space" class.)
368    4.  A partial match never returns an empty string (because you can always
369        match an empty string at the end of the subject); however the checking for
370        an empty string was starting at the "start of match" point. This has been
371        changed to the "earliest inspected character" point, because the returned
372        data for a partial match starts at this character. This means that, for
373        example, /(?<=abc)def/ gives a partial match for the subject "abc"
374        (previously it gave "no match").
376    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
377        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
378        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
379        has an implication that the given string is incomplete (because a partial
380        match is preferred over a full match). For this reason, these items now
381        give a partial match in this situation. [Aside: previously, the one case
382        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
383        match rather than a full match, which was wrong by the old rules, but is
384        now correct.]
386    6.  There was a bug in the handling of #-introduced comments, recognized when
387        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
388        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
389        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
390        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
391        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
392        places in pcre_compile().
394    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
395        comments when looking ahead for named forward references to subpatterns,
396        the only newline sequence it recognized was NL. It now handles newlines
397        according to the set newline convention.
399    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
400        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
401        cater for a lack of strerror(). These oversights have been fixed.
403    9.  Added --match-limit and --recursion-limit to pcregrep.
405    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
407    11. When the -o option was used, pcregrep was setting a return code of 1, even
408        when matches were found, and --line-buffered was not being honoured.
410    12. Added an optional parentheses number to the -o and --only-matching options
411        of pcregrep.
413    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
414        can match an empty string. The code to do it in pcretest and pcredemo
415        needed fixing:
417        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
418            only one byte after an empty string match just before CRLF (this case
419            just got forgotten; "any" and "anycrlf" were OK).
421        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
422            mode when an empty string match preceded an ASCII character followed by
423            a non-ASCII character. (The code for advancing by one character rather
424            than one byte was nonsense.)
426        (c) The pcredemo.c sample program did not have any code at all to handle
427            the cases when CRLF is a valid newline sequence.
429    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
430        as a starting offset was within the subject string. There is now a new
431        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
432        negative or greater than the length of the string. In order to test this,
433        pcretest is extended to allow the setting of negative starting offsets.
435    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
436        starting offset points to the beginning of a UTF-8 character was
437        unnecessarily clumsy. I tidied it up.
439    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
440        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
442    17. Nobody had reported that the --include_dir option, which was added in
443        release 7.7 should have been called --include-dir (hyphen, not underscore)
444        for compatibility with GNU grep. I have changed it to --include-dir, but
445        left --include_dir as an undocumented synonym, and the same for
446        --exclude-dir, though that is not available in GNU grep, at least as of
447        release 2.5.4.
449    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
450        characters from a string of bytes) have been redefined so as not to use
451        loops, in order to improve performance in some environments. At the same
452        time, I abstracted some of the common code into auxiliary macros to save
453        repetition (this should not affect the compiled code).
455    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
456        compile-time error is now given if \c is not followed by an ASCII
457        character, that is, a byte less than 128. (In EBCDIC mode, the code is
458        different, and any byte value is allowed.)
460    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
461        START_OPTIMIZE option, which is now allowed at compile time - but just
462        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
463        to pcregrep and other applications that have no direct access to PCRE
464        options. The new /Y option in pcretest sets this option when calling
465        pcre_compile().
467    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
468        back references. Groups containing recursive back references were forced to
469        be atomic by that change, but in the case of named groups, the amount of
470        memory required was incorrectly computed, leading to "Failed: internal
471        error: code overflow". This has been fixed.
473    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
474        pcretest.c, to avoid build problems in some Borland environments.
477    Version 8.10 25-Jun-2010
478    ------------------------
480    1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
481        THEN.
483    2.  (*ACCEPT) was not working when inside an atomic group.
485    3.  Inside a character class, \B is treated as a literal by default, but
486        faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
487        causes the error). The code is unchanged, but I tidied the documentation.
489    4.  Inside a character class, PCRE always treated \R and \X as literals,
490        whereas Perl faults them if its -w option is set. I have changed PCRE so
491        that it faults them when PCRE_EXTRA is set.
493    5.  Added support for \N, which always matches any character other than
494        newline. (It is the same as "." when PCRE_DOTALL is not set.)
496    6.  When compiling pcregrep with newer versions of gcc which may have
497        FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
498        declared with attribute warn_unused_result" were given. Just casting the
499        result to (void) does not stop the warnings; a more elaborate fudge is
500        needed. I've used a macro to implement this.
502    7.  Minor change to pcretest.c to avoid a compiler warning.
504    8.  Added four artifical Unicode properties to help with an option to make
505        \s etc use properties (see next item). The new properties are: Xan
506        (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
508    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
509        use Unicode properties. (*UCP) at the start of a pattern can be used to set
510        this option. Modified pcretest to add /W to test this facility. Added
511        REG_UCP to make it available via the POSIX interface.
513    10. Added --line-buffered to pcregrep.
515    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
516        studied, and the match started with a letter with a code point greater than
517        127 whose first byte was different to the first byte of the other case of
518        the letter, the other case of this starting letter was not recognized
519        (#976).
521    12. If a pattern that was studied started with a repeated Unicode property
522        test, for example, \p{Nd}+, there was the theoretical possibility of
523        setting up an incorrect bitmap of starting bytes, but fortunately it could
524        not have actually happened in practice until change 8 above was made (it
525        added property types that matched character-matching opcodes).
527    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
528        possible starting bytes for non-anchored patterns.
530    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
531        \R, and also a number of cases that involve Unicode properties, both
532        explicit and implicit when PCRE_UCP is set.
534    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
535        input, it could crash or give wrong results if characters with values
536        greater than 0xc0 were present in the subject string. (Detail: it assumed
537        UTF-8 input when processing these items.)
539    16. Added a lot of (int) casts to avoid compiler warnings in systems where
540        size_t is 64-bit (#991).
542    17. Added a check for running out of memory when PCRE is compiled with
543        --disable-stack-for-recursion (#990).
545    18. If the last data line in a file for pcretest does not have a newline on
546        the end, a newline was missing in the output.
548    19. The default pcre_chartables.c file recognizes only ASCII characters (values
549        less than 128) in its various bitmaps. However, there is a facility for
550        generating tables according to the current locale when PCRE is compiled. It
551        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
552        characters, are recognized by isspace() and therefore were getting set in
553        these tables, and indeed these tables seem to approximate to ISO 8859. This
554        caused a problem in UTF-8 mode when pcre_study() was used to create a list
555        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
556        which of course cannot start UTF-8 characters. I have changed the code so
557        that only real ASCII characters (less than 128) and the correct starting
558        bytes for UTF-8 encodings are set for characters greater than 127 when in
559        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
560        altogether.)
562    20. Added the /T option to pcretest so as to be able to run tests with non-
563        standard character tables, thus making it possible to include the tests
564        used for 19 above in the standard set of tests.
566    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
567        reference to a subpattern the other side of a comment that contains an
568        opening parenthesis caused either an internal compiling error, or a
569        reference to the wrong subpattern.
572    Version 8.02 19-Mar-2010
573    ------------------------
575    1.  The Unicode data tables have been updated to Unicode 5.2.0.
577    2.  Added the option --libs-cpp to pcre-config, but only when C++ support is
578        configured.
580    3.  Updated the licensing terms in the pcregexp.pas file, as agreed with the
581        original author of that file, following a query about its status.
583    4.  On systems that do not have stdint.h (e.g. Solaris), check for and include
584        inttypes.h instead. This fixes a bug that was introduced by change 8.01/8.
586    5.  A pattern such as (?&t)*+(?(DEFINE)(?<t>.)) which has a possessive
587        quantifier applied to a forward-referencing subroutine call, could compile
588        incorrect code or give the error "internal error: previously-checked
589        referenced subpattern not found".
591    6.  Both MS Visual Studio and Symbian OS have problems with initializing
592        variables to point to external functions. For these systems, therefore,
593        pcre_malloc etc. are now initialized to local functions that call the
594        relevant global functions.
596    7.  There were two entries missing in the vectors called coptable and poptable
597        in pcre_dfa_exec.c. This could lead to memory accesses outsize the vectors.
598        I've fixed the data, and added a kludgy way of testing at compile time that
599        the lengths are correct (equal to the number of opcodes).
601    8.  Following on from 7, I added a similar kludge to check the length of the
602        eint vector in pcreposix.c.
604    9.  Error texts for pcre_compile() are held as one long string to avoid too
605        much relocation at load time. To find a text, the string is searched,
606        counting zeros. There was no check for running off the end of the string,
607        which could happen if a new error number was added without updating the
608        string.
610    10. \K gave a compile-time error if it appeared in a lookbehind assersion.
612    11. \K was not working if it appeared in an atomic group or in a group that
613        was called as a "subroutine", or in an assertion. Perl 5.11 documents that
614        \K is "not well defined" if used in an assertion. PCRE now accepts it if
615        the assertion is positive, but not if it is negative.
617    12. Change 11 fortuitously reduced the size of the stack frame used in the
618        "match()" function of pcre_exec.c by one pointer. Forthcoming
619        implementation of support for (*MARK) will need an extra pointer on the
620        stack; I have reserved it now, so that the stack frame size does not
621        decrease.
623    13. A pattern such as (?P<L1>(?P<L2>0)|(?P>L2)(?P>L1)) in which the only other
624        item in branch that calls a recursion is a subroutine call - as in the
625        second branch in the above example - was incorrectly given the compile-
626        time error "recursive call could loop indefinitely" because pcre_compile()
627        was not correctly checking the subroutine for matching a non-empty string.
629    14. The checks for overrunning compiling workspace could trigger after an
630        overrun had occurred. This is a "should never occur" error, but it can be
631        triggered by pathological patterns such as hundreds of nested parentheses.
632        The checks now trigger 100 bytes before the end of the workspace.
634    15. Fix typo in configure.ac: "srtoq" should be "strtoq".
637    Version 8.01 19-Jan-2010
638    ------------------------
640  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
641      particular, this includes all (DEFINE) patterns), a call to pcre_study()      particular, this includes all (*DEFINE) patterns), a call to pcre_study()
642      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
643      subpatterns).      subpatterns). This could cause incorrect "no match" results.
645  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
646      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 06-Jan-10 Line 694  Version 8.01 06-Jan-10
694      custom one, because of the following reported problem in Windows:      custom one, because of the following reported problem in Windows:
696        - libbz2 uses the Pascal calling convention (WINAPI) for the functions        - libbz2 uses the Pascal calling convention (WINAPI) for the functions
697          under Win32.            under Win32.
698        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",        - The standard autoconf AC_CHECK_LIB fails to include "bzlib.h",
699          therefore missing the function definition.            therefore missing the function definition.
700        - The compiler thus generates a "C" signature for the test function.        - The compiler thus generates a "C" signature for the test function.
701        - The linker fails to find the "C" function.        - The linker fails to find the "C" function.
702        - PCRE fails to configure if asked to do so against libbz2.        - PCRE fails to configure if asked to do so against libbz2.
# Line 113  Version 8.01 06-Jan-10 Line 746  Version 8.01 06-Jan-10
746      equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for      equivalent. It's not enough to call AC_CHECK_FUNCS: hpux has a strtoll, for
747      instance, but it only takes 2 args instead of 3!"      instance, but it only takes 2 args instead of 3!"
749    18. A subtle bug concerned with back references has been fixed by a change of
750        specification, with a corresponding code fix. A pattern such as
751        ^(xa|=?\1a)+$ which contains a back reference inside the group to which it
752        refers, was giving matches when it shouldn't. For example, xa=xaaa would
753        match that pattern. Interestingly, Perl (at least up to 5.11.3) has the
754        same bug. Such groups have to be quantified to be useful, or contained
755        inside another quantified group. (If there's no repetition, the reference
756        can never match.) The problem arises because, having left the group and
757        moved on to the rest of the pattern, a later failure that backtracks into
758        the group uses the captured value from the final iteration of the group
759        rather than the correct earlier one. I have fixed this in PCRE by forcing
760        any group that contains a reference to itself to be an atomic group; that
761        is, there cannot be any backtracking into it once it has completed. This is
762        similar to recursive and subroutine calls.
765  Version 8.00 19-Oct-09  Version 8.00 19-Oct-09
766  ----------------------  ----------------------

Removed from v.486  
changed lines
  Added in v.701

  ViewVC Help
Powered by ViewVC 1.1.5