ViewVC logotype

Diff of /code/trunk/ChangeLog

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

revision 517 by ph10, Wed May 5 10:44:20 2010 UTC revision 663 by ph10, Mon Aug 22 14:53:12 2011 UTC
# Line 1  Line 1 
1  ChangeLog for PCRE  ChangeLog for PCRE
2  ------------------  ------------------
4  Version 8.10 03 May-2010  Version 8.20
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.
12    2. If a pattern such as /(a)b|ac/ is matched against "ac", there is no captured
13       substring, but while checking the failing first alternative, substring 1 is
14       temporarily captured. If the output vector supplied to pcre_exec() was not
15       big enough for this capture, the yield of the function was still zero
16       ("insufficient space for captured substrings"). This cannot be totally fixed
17       without adding another stack variable, which seems a lot of expense for a
18       edge case. However, I have improved the situation in cases such as
19       /(a)(b)x|abc/ matched against "abc", where the return code indicates that
20       fewer than the maximum number of slots in the ovector have been set.
22    3. Related to (2) above: when there are more back references in a pattern than
23       slots in the output vector, pcre_exec() uses temporary memory during
24       matching, and copies in the captures as far as possible afterwards. It was
25       using the entire output vector, but this conflicts with the specification
26       that only 2/3 is used for passing back captured substrings. Now it uses only
27       the first 2/3, for compatibility. This is, of course, another edge case.
30    Version 8.13 16-Aug-2011
31    ------------------------
33    1.  The Unicode data tables have been updated to Unicode 6.0.0.
35    2.  Two minor typos in pcre_internal.h have been fixed.
37    3.  Added #include <string.h> to pcre_scanner_unittest.cc, pcrecpp.cc, and
38        pcrecpp_unittest.cc. They are needed for strcmp(), memset(), and strchr()
39        in some environments (e.g. Solaris 10/SPARC using Sun Studio 12U2).
41    4.  There were a number of related bugs in the code for matching backrefences
42        caselessly in UTF-8 mode when codes for the characters concerned were
43        different numbers of bytes. For example, U+023A and U+2C65 are an upper
44        and lower case pair, using 2 and 3 bytes, respectively. The main bugs were:
45        (a) A reference to 3 copies of a 2-byte code matched only 2 of a 3-byte
46        code. (b) A reference to 2 copies of a 3-byte code would not match 2 of a
47        2-byte code at the end of the subject (it thought there wasn't enough data
48        left).
50    5.  Comprehensive information about what went wrong is now returned by
51        pcre_exec() and pcre_dfa_exec() when the UTF-8 string check fails, as long
52        as the output vector has at least 2 elements. The offset of the start of
53        the failing character and a reason code are placed in the vector.
55    6.  When the UTF-8 string check fails for pcre_compile(), the offset that is
56        now returned is for the first byte of the failing character, instead of the
57        last byte inspected. This is an incompatible change, but I hope it is small
58        enough not to be a problem. It makes the returned offset consistent with
59        pcre_exec() and pcre_dfa_exec().
61    7.  pcretest now gives a text phrase as well as the error number when
62        pcre_exec() or pcre_dfa_exec() fails; if the error is a UTF-8 check
63        failure, the offset and reason code are output.
65    8.  When \R was used with a maximizing quantifier it failed to skip backwards
66        over a \r\n pair if the subsequent match failed. Instead, it just skipped
67        back over a single character (\n). This seems wrong (because it treated the
68        two characters as a single entity when going forwards), conflicts with the
69        documentation that \R is equivalent to (?>\r\n|\n|...etc), and makes the
70        behaviour of \R* different to (\R)*, which also seems wrong. The behaviour
71        has been changed.
73    9.  Some internal refactoring has changed the processing so that the handling
74        of the PCRE_CASELESS and PCRE_MULTILINE options is done entirely at compile
75        time (the PCRE_DOTALL option was changed this way some time ago: version
76        7.7 change 16). This has made it possible to abolish the OP_OPT op code,
77        which was always a bit of a fudge. It also means that there is one less
78        argument for the match() function, which reduces its stack requirements
79        slightly. This change also fixes an incompatibility with Perl: the pattern
80        (?i:([^b]))(?1) should not match "ab", but previously PCRE gave a match.
82    10. More internal refactoring has drastically reduced the number of recursive
83        calls to match() for possessively repeated groups such as (abc)++ when
84        using pcre_exec().
86    11. While implementing 10, a number of bugs in the handling of groups were
87        discovered and fixed:
89        (?<=(a)+) was not diagnosed as invalid (non-fixed-length lookbehind).
90        (a|)*(?1) gave a compile-time internal error.
91        ((a|)+)+  did not notice that the outer group could match an empty string.
92        (^a|^)+   was not marked as anchored.
93        (.*a|.*)+ was not marked as matching at start or after a newline.
95    12. Yet more internal refactoring has removed another argument from the match()
96        function. Special calls to this function are now indicated by setting a
97        value in a variable in the "match data" data block.
99    13. Be more explicit in pcre_study() instead of relying on "default" for
100        opcodes that mean there is no starting character; this means that when new
101        ones are added and accidentally left out of pcre_study(), testing should
102        pick them up.
104    14. The -s option of pcretest has been documented for ages as being an old
105        synonym of -m (show memory usage). I have changed it to mean "force study
106        for every regex", that is, assume /S for every regex. This is similar to -i
107        and -d etc. It's slightly incompatible, but I'm hoping nobody is still
108        using it. It makes it easier to run collections of tests with and without
109        study enabled, and thereby test pcre_study() more easily. All the standard
110        tests are now run with and without -s (but some patterns can be marked as
111        "never study" - see 20 below).
113    15. When (*ACCEPT) was used in a subpattern that was called recursively, the
114        restoration of the capturing data to the outer values was not happening
115        correctly.
117    16. If a recursively called subpattern ended with (*ACCEPT) and matched an
118        empty string, and PCRE_NOTEMPTY was set, pcre_exec() thought the whole
119        pattern had matched an empty string, and so incorrectly returned a no
120        match.
122    17. There was optimizing code for the last branch of non-capturing parentheses,
123        and also for the obeyed branch of a conditional subexpression, which used
124        tail recursion to cut down on stack usage. Unfortunately, now that there is
125        the possibility of (*THEN) occurring in these branches, tail recursion is
126        no longer possible because the return has to be checked for (*THEN). These
127        two optimizations have therefore been removed.
129    18. If a pattern containing \R was studied, it was assumed that \R always
130        matched two bytes, thus causing the minimum subject length to be
131        incorrectly computed because \R can also match just one byte.
133    19. If a pattern containing (*ACCEPT) was studied, the minimum subject length
134        was incorrectly computed.
136    20. If /S is present twice on a test pattern in pcretest input, it now
137        *disables* studying, thereby overriding the use of -s on the command line
138        (see 14 above). This is necessary for one or two tests to keep the output
139        identical in both cases.
141    21. When (*ACCEPT) was used in an assertion that matched an empty string and
142        PCRE_NOTEMPTY was set, PCRE applied the non-empty test to the assertion.
144    22. When an atomic group that contained a capturing parenthesis was
145        successfully matched, but the branch in which it appeared failed, the
146        capturing was not being forgotten if a higher numbered group was later
147        captured. For example, /(?>(a))b|(a)c/ when matching "ac" set capturing
148        group 1 to "a", when in fact it should be unset. This applied to multi-
149        branched capturing and non-capturing groups, repeated or not, and also to
150        positive assertions (capturing in negative assertions does not happen
151        in PCRE) and also to nested atomic groups.
153    23. Add the ++ qualifier feature to pcretest, to show the remainder of the
154        subject after a captured substring, to make it easier to tell which of a
155        number of identical substrings has been captured.
157    24. The way atomic groups are processed by pcre_exec() has been changed so that
158        if they are repeated, backtracking one repetition now resets captured
159        values correctly. For example, if ((?>(a+)b)+aabab) is matched against
160        "aaaabaaabaabab" the value of captured group 2 is now correctly recorded as
161        "aaa". Previously, it would have been "a". As part of this code
162        refactoring, the way recursive calls are handled has also been changed.
164    25. If an assertion condition captured any substrings, they were not passed
165        back unless some other capturing happened later. For example, if
166        (?(?=(a))a) was matched against "a", no capturing was returned.
168    26. When studying a pattern that contained subroutine calls or assertions,
169        the code for finding the minimum length of a possible match was handling
170        direct recursions such as (xxx(?1)|yyy) but not mutual recursions (where
171        group 1 called group 2 while simultaneously a separate group 2 called group
172        1). A stack overflow occurred in this case. I have fixed this by limiting
173        the recursion depth to 10.
175    27. Updated RunTest.bat in the distribution to the version supplied by Tom
176        Fortmann. This supports explicit test numbers on the command line, and has
177        argument validation and error reporting.
179    28. An instance of \X with an unlimited repeat could fail if at any point the
180        first character it looked at was a mark character.
182    29. Some minor code refactoring concerning Unicode properties and scripts
183        should reduce the stack requirement of match() slightly.
185    30. Added the '=' option to pcretest to check the setting of unused capturing
186        slots at the end of the pattern, which are documented as being -1, but are
187        not included in the return count.
189    31. If \k was not followed by a braced, angle-bracketed, or quoted name, PCRE
190        compiled something random. Now it gives a compile-time error (as does
191        Perl).
193    32. A *MARK encountered during the processing of a positive assertion is now
194        recorded and passed back (compatible with Perl).
196    33. If --only-matching or --colour was set on a pcregrep call whose pattern
197        had alternative anchored branches, the search for a second match in a line
198        was done as if at the line start. Thus, for example, /^01|^02/ incorrectly
199        matched the line "0102" twice. The same bug affected patterns that started
200        with a backwards assertion. For example /\b01|\b02/ also matched "0102"
201        twice.
203    34. Previously, PCRE did not allow quantification of assertions. However, Perl
204        does, and because of capturing effects, quantifying parenthesized
205        assertions may at times be useful. Quantifiers are now allowed for
206        parenthesized assertions.
208    35. A minor code tidy in pcre_compile() when checking options for \R usage.
210    36. \g was being checked for fancy things in a character class, when it should
211        just be a literal "g".
213    37. PCRE was rejecting [:a[:digit:]] whereas Perl was not. It seems that the
214        appearance of a nested POSIX class supersedes an apparent external class.
215        For example, [:a[:digit:]b:] matches "a", "b", ":", or a digit. Also,
216        unescaped square brackets may also appear as part of class names. For
217        example, [:a[:abc]b:] gives unknown class "[:abc]b:]". PCRE now behaves
218        more like Perl. (But see 8.20/1 above.)
220    38. PCRE was giving an error for \N with a braced quantifier such as {1,} (this
221        was because it thought it was \N{name}, which is not supported).
223    39. Add minix to OS list not supporting the -S option in pcretest.
225    40. PCRE tries to detect cases of infinite recursion at compile time, but it
226        cannot analyze patterns in sufficient detail to catch mutual recursions
227        such as ((?1))((?2)). There is now a runtime test that gives an error if a
228        subgroup is called recursively as a subpattern for a second time at the
229        same position in the subject string. In previous releases this might have
230        been caught by the recursion limit, or it might have run out of stack.
232    41. A pattern such as /(?(R)a+|(?R)b)/ is quite safe, as the recursion can
233        happen only once. PCRE was, however incorrectly giving a compile time error
234        "recursive call could loop indefinitely" because it cannot analyze the
235        pattern in sufficient detail. The compile time test no longer happens when
236        PCRE is compiling a conditional subpattern, but actual runaway loops are
237        now caught at runtime (see 40 above).
239    42. It seems that Perl allows any characters other than a closing parenthesis
240        to be part of the NAME in (*MARK:NAME) and other backtracking verbs. PCRE
241        has been changed to be the same.
243    43. Updated configure.ac to put in more quoting round AC_LANG_PROGRAM etc. so
244        as not to get warnings when autogen.sh is called. Also changed
245        AC_PROG_LIBTOOL (deprecated) to LT_INIT (the current macro).
247    44. To help people who use pcregrep to scan files containing exceedingly long
248        lines, the following changes have been made:
250        (a) The default value of the buffer size parameter has been increased from
251            8K to 20K. (The actual buffer used is three times this size.)
253        (b) The default can be changed by ./configure --with-pcregrep-bufsize when
254            PCRE is built.
256        (c) A --buffer-size=n option has been added to pcregrep, to allow the size
257            to be set at run time.
259        (d) Numerical values in pcregrep options can be followed by K or M, for
260            example --buffer-size=50K.
262        (e) If a line being scanned overflows pcregrep's buffer, an error is now
263            given and the return code is set to 2.
265    45. Add a pointer to the latest mark to the callout data block.
267    46. The pattern /.(*F)/, when applied to "abc" with PCRE_PARTIAL_HARD, gave a
268        partial match of an empty string instead of no match. This was specific to
269        the use of ".".
271    47. The pattern /f.*/8s, when applied to "for" with PCRE_PARTIAL_HARD, gave a
272        complete match instead of a partial match. This bug was dependent on both
273        the PCRE_UTF8 and PCRE_DOTALL options being set.
275    48. For a pattern such as /\babc|\bdef/ pcre_study() was failing to set up the
276        starting byte set, because \b was not being ignored.
279    Version 8.12 15-Jan-2011
280    ------------------------
282    1.  Fixed some typos in the markup of the man pages, and wrote a script that
283        checks for such things as part of the documentation building process.
285    2.  On a big-endian 64-bit system, pcregrep did not correctly process the
286        --match-limit and --recursion-limit options (added for 8.11). In
287        particular, this made one of the standard tests fail. (The integer value
288        went into the wrong half of a long int.)
290    3.  If the --colour option was given to pcregrep with -v (invert match), it
291        did strange things, either producing crazy output, or crashing. It should,
292        of course, ignore a request for colour when reporting lines that do not
293        match.
295    4.  Another pcregrep bug caused similar problems if --colour was specified with
296        -M (multiline) and the pattern match finished with a line ending.
298    5.  In pcregrep, when a pattern that ended with a literal newline sequence was
299        matched in multiline mode, the following line was shown as part of the
300        match. This seems wrong, so I have changed it.
302    6.  Another pcregrep bug in multiline mode, when --colour was specified, caused
303        the check for further matches in the same line (so they could be coloured)
304        to overrun the end of the current line. If another match was found, it was
305        incorrectly shown (and then shown again when found in the next line).
307    7.  If pcregrep was compiled under Windows, there was a reference to the
308        function pcregrep_exit() before it was defined. I am assuming this was
309        the cause of the "error C2371: 'pcregrep_exit' : redefinition;" that was
310        reported by a user. I've moved the definition above the reference.
313    Version 8.11 10-Dec-2010
314    ------------------------
316    1.  (*THEN) was not working properly if there were untried alternatives prior
317        to it in the current branch. For example, in ((a|b)(*THEN)(*F)|c..) it
318        backtracked to try for "b" instead of moving to the next alternative branch
319        at the same level (in this case, to look for "c"). The Perl documentation
320        is clear that when (*THEN) is backtracked onto, it goes to the "next
321        alternative in the innermost enclosing group".
323    2.  (*COMMIT) was not overriding (*THEN), as it does in Perl. In a pattern
324        such as   (A(*COMMIT)B(*THEN)C|D)  any failure after matching A should
325        result in overall failure. Similarly, (*COMMIT) now overrides (*PRUNE) and
326        (*SKIP), (*SKIP) overrides (*PRUNE) and (*THEN), and (*PRUNE) overrides
327        (*THEN).
329    3.  If \s appeared in a character class, it removed the VT character from
330        the class, even if it had been included by some previous item, for example
331        in [\x00-\xff\s]. (This was a bug related to the fact that VT is not part
332        of \s, but is part of the POSIX "space" class.)
334    4.  A partial match never returns an empty string (because you can always
335        match an empty string at the end of the subject); however the checking for
336        an empty string was starting at the "start of match" point. This has been
337        changed to the "earliest inspected character" point, because the returned
338        data for a partial match starts at this character. This means that, for
339        example, /(?<=abc)def/ gives a partial match for the subject "abc"
340        (previously it gave "no match").
342    5.  Changes have been made to the way PCRE_PARTIAL_HARD affects the matching
343        of $, \z, \Z, \b, and \B. If the match point is at the end of the string,
344        previously a full match would be given. However, setting PCRE_PARTIAL_HARD
345        has an implication that the given string is incomplete (because a partial
346        match is preferred over a full match). For this reason, these items now
347        give a partial match in this situation. [Aside: previously, the one case
348        /t\b/ matched against "cat" with PCRE_PARTIAL_HARD set did return a partial
349        match rather than a full match, which was wrong by the old rules, but is
350        now correct.]
352    6.  There was a bug in the handling of #-introduced comments, recognized when
353        PCRE_EXTENDED is set, when PCRE_NEWLINE_ANY and PCRE_UTF8 were also set.
354        If a UTF-8 multi-byte character included the byte 0x85 (e.g. +U0445, whose
355        UTF-8 encoding is 0xd1,0x85), this was misinterpreted as a newline when
356        scanning for the end of the comment. (*Character* 0x85 is an "any" newline,
357        but *byte* 0x85 is not, in UTF-8 mode). This bug was present in several
358        places in pcre_compile().
360    7.  Related to (6) above, when pcre_compile() was skipping #-introduced
361        comments when looking ahead for named forward references to subpatterns,
362        the only newline sequence it recognized was NL. It now handles newlines
363        according to the set newline convention.
365    8.  SunOS4 doesn't have strerror() or strtoul(); pcregrep dealt with the
366        former, but used strtoul(), whereas pcretest avoided strtoul() but did not
367        cater for a lack of strerror(). These oversights have been fixed.
369    9.  Added --match-limit and --recursion-limit to pcregrep.
371    10. Added two casts needed to build with Visual Studio when NO_RECURSE is set.
373    11. When the -o option was used, pcregrep was setting a return code of 1, even
374        when matches were found, and --line-buffered was not being honoured.
376    12. Added an optional parentheses number to the -o and --only-matching options
377        of pcregrep.
379    13. Imitating Perl's /g action for multiple matches is tricky when the pattern
380        can match an empty string. The code to do it in pcretest and pcredemo
381        needed fixing:
383        (a) When the newline convention was "crlf", pcretest got it wrong, skipping
384            only one byte after an empty string match just before CRLF (this case
385            just got forgotten; "any" and "anycrlf" were OK).
387        (b) The pcretest code also had a bug, causing it to loop forever in UTF-8
388            mode when an empty string match preceded an ASCII character followed by
389            a non-ASCII character. (The code for advancing by one character rather
390            than one byte was nonsense.)
392        (c) The pcredemo.c sample program did not have any code at all to handle
393            the cases when CRLF is a valid newline sequence.
395    14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
396        as a starting offset was within the subject string. There is now a new
397        error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is
398        negative or greater than the length of the string. In order to test this,
399        pcretest is extended to allow the setting of negative starting offsets.
401    15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the
402        starting offset points to the beginning of a UTF-8 character was
403        unnecessarily clumsy. I tidied it up.
405    16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
406        bad UTF-8 sequence and one that is incomplete when using PCRE_PARTIAL_HARD.
408    17. Nobody had reported that the --include_dir option, which was added in
409        release 7.7 should have been called --include-dir (hyphen, not underscore)
410        for compatibility with GNU grep. I have changed it to --include-dir, but
411        left --include_dir as an undocumented synonym, and the same for
412        --exclude-dir, though that is not available in GNU grep, at least as of
413        release 2.5.4.
415    18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8
416        characters from a string of bytes) have been redefined so as not to use
417        loops, in order to improve performance in some environments. At the same
418        time, I abstracted some of the common code into auxiliary macros to save
419        repetition (this should not affect the compiled code).
421    19. If \c was followed by a multibyte UTF-8 character, bad things happened. A
422        compile-time error is now given if \c is not followed by an ASCII
423        character, that is, a byte less than 128. (In EBCDIC mode, the code is
424        different, and any byte value is allowed.)
426    20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
427        START_OPTIMIZE option, which is now allowed at compile time - but just
428        passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
429        to pcregrep and other applications that have no direct access to PCRE
430        options. The new /Y option in pcretest sets this option when calling
431        pcre_compile().
433    21. Change 18 of release 8.01 broke the use of named subpatterns for recursive
434        back references. Groups containing recursive back references were forced to
435        be atomic by that change, but in the case of named groups, the amount of
436        memory required was incorrectly computed, leading to "Failed: internal
437        error: code overflow". This has been fixed.
439    22. Some patches to pcre_stringpiece.h, pcre_stringpiece_unittest.cc, and
440        pcretest.c, to avoid build problems in some Borland environments.
443    Version 8.10 25-Jun-2010
444  ------------------------  ------------------------
446  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and  1.  Added support for (*MARK:ARG) and for ARG additions to PRUNE, SKIP, and
# Line 9  Version 8.10 03 May-2010 Line 448  Version 8.10 03 May-2010
449  2.  (*ACCEPT) was not working when inside an atomic group.  2.  (*ACCEPT) was not working when inside an atomic group.
451  3.  Inside a character class, \B is treated as a literal by default, but  3.  Inside a character class, \B is treated as a literal by default, but
452      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option      faulted if PCRE_EXTRA is set. This mimics Perl's behaviour (the -w option
453      causes the error). The code is unchanged, but I tidied the documentation.      causes the error). The code is unchanged, but I tidied the documentation.
455  4.  Inside a character class, PCRE always treated \R and \X as literals,  4.  Inside a character class, PCRE always treated \R and \X as literals,
456      whereas Perl faults them if its -w option is set. I have changed PCRE so      whereas Perl faults them if its -w option is set. I have changed PCRE so
457      that it faults them when PCRE_EXTRA is set.      that it faults them when PCRE_EXTRA is set.
459  5.  Added support for \N, which always matches any character other than  5.  Added support for \N, which always matches any character other than
460      newline. (It is the same as "." when PCRE_DOTALL is not set.)      newline. (It is the same as "." when PCRE_DOTALL is not set.)
462  6.  When compiling pcregrep with newer versions of gcc which may have  6.  When compiling pcregrep with newer versions of gcc which may have
463      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',      FORTIFY_SOURCE set, several warnings "ignoring return value of 'fwrite',
464      declared with attribute warn_unused_result" were given. Just casting the      declared with attribute warn_unused_result" were given. Just casting the
465      result to (void) does not stop the warnings; a more elaborate fudge is      result to (void) does not stop the warnings; a more elaborate fudge is
466      needed. I've used a macro to implement this.      needed. I've used a macro to implement this.
468  7.  Minor change to pcretest.c to avoid a compiler warning.  7.  Minor change to pcretest.c to avoid a compiler warning.
470  8.  Added four artifical Unicode properties to help with an option to make  8.  Added four artifical Unicode properties to help with an option to make
471      \s etc use properties. The new properties are: Xan (alphanumeric), Xsp      \s etc use properties (see next item). The new properties are: Xan
472      (Perl space), Xps (POSIX space), and Xwd (word).      (alphanumeric), Xsp (Perl space), Xps (POSIX space), and Xwd (word).
474    9.  Added PCRE_UCP to make \b, \d, \s, \w, and certain POSIX character classes
475        use Unicode properties. (*UCP) at the start of a pattern can be used to set
476        this option. Modified pcretest to add /W to test this facility. Added
477        REG_UCP to make it available via the POSIX interface.
479    10. Added --line-buffered to pcregrep.
481    11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was
482        studied, and the match started with a letter with a code point greater than
483        127 whose first byte was different to the first byte of the other case of
484        the letter, the other case of this starting letter was not recognized
485        (#976).
487    12. If a pattern that was studied started with a repeated Unicode property
488        test, for example, \p{Nd}+, there was the theoretical possibility of
489        setting up an incorrect bitmap of starting bytes, but fortunately it could
490        not have actually happened in practice until change 8 above was made (it
491        added property types that matched character-matching opcodes).
493    13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of
494        possible starting bytes for non-anchored patterns.
496    14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
497        \R, and also a number of cases that involve Unicode properties, both
498        explicit and implicit when PCRE_UCP is set.
500    15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
501        input, it could crash or give wrong results if characters with values
502        greater than 0xc0 were present in the subject string. (Detail: it assumed
503        UTF-8 input when processing these items.)
505    16. Added a lot of (int) casts to avoid compiler warnings in systems where
506        size_t is 64-bit (#991).
508    17. Added a check for running out of memory when PCRE is compiled with
509        --disable-stack-for-recursion (#990).
511    18. If the last data line in a file for pcretest does not have a newline on
512        the end, a newline was missing in the output.
514    19. The default pcre_chartables.c file recognizes only ASCII characters (values
515        less than 128) in its various bitmaps. However, there is a facility for
516        generating tables according to the current locale when PCRE is compiled. It
517        turns out that in some environments, 0x85 and 0xa0, which are Unicode space
518        characters, are recognized by isspace() and therefore were getting set in
519        these tables, and indeed these tables seem to approximate to ISO 8859. This
520        caused a problem in UTF-8 mode when pcre_study() was used to create a list
521        of bytes that can start a match. For \s, it was including 0x85 and 0xa0,
522        which of course cannot start UTF-8 characters. I have changed the code so
523        that only real ASCII characters (less than 128) and the correct starting
524        bytes for UTF-8 encodings are set for characters greater than 127 when in
525        UTF-8 mode. (When PCRE_UCP is set - see 9 above - the code is different
526        altogether.)
528    20. Added the /T option to pcretest so as to be able to run tests with non-
529        standard character tables, thus making it possible to include the tests
530        used for 19 above in the standard set of tests.
532    21. A pattern such as (?&t)(?#()(?(DEFINE)(?<t>a)) which has a forward
533        reference to a subpattern the other side of a comment that contains an
534        opening parenthesis caused either an internal compiling error, or a
535        reference to the wrong subpattern.
538  Version 8.02 19-Mar-2010  Version 8.02 19-Mar-2010

Removed from v.517  
changed lines
  Added in v.663

  ViewVC Help
Powered by ViewVC 1.1.5