| 42 |
11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was |
11. In UTF-8 mode, if a pattern that was compiled with PCRE_CASELESS was |
| 43 |
studied, and the match started with a letter with a code point greater than |
studied, and the match started with a letter with a code point greater than |
| 44 |
127 whose first byte was different to the first byte of the other case of |
127 whose first byte was different to the first byte of the other case of |
| 45 |
the letter, the other case of this starting letter was not recognized. |
the letter, the other case of this starting letter was not recognized |
| 46 |
|
(#976). |
| 47 |
|
|
| 48 |
12. pcreposix.c included pcre.h before including pcre_internal.h. This caused a |
12. If a pattern that was studied started with a repeated Unicode property |
|
conflict in the definition of PCRE_EXP_DECL. I have removed the include of |
|
|
pcre.h as pcre_internal.h includes pcre.h itself. (This may be a bit of |
|
|
historical tidying that never got done.) |
|
|
|
|
|
13. If a pattern that was studied started with a repeated Unicode property |
|
| 49 |
test, for example, \p{Nd}+, there was the theoretical possibility of |
test, for example, \p{Nd}+, there was the theoretical possibility of |
| 50 |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
| 51 |
not have actually happened in practice until change 8 above was made (it |
not have actually happened in practice until change 8 above was made (it |
| 52 |
added property types that matched character-matching opcodes). |
added property types that matched character-matching opcodes). |
| 53 |
|
|
| 54 |
14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of |
13. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of |
| 55 |
possible starting bytes for non-anchored patterns. |
possible starting bytes for non-anchored patterns. |
| 56 |
|
|
| 57 |
15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes |
14. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes |
| 58 |
\R, and also a number of cases that involve Unicode properties, both |
\R, and also a number of cases that involve Unicode properties, both |
| 59 |
explicit and implicit when PCRE_UCP is set. |
explicit and implicit when PCRE_UCP is set. |
| 60 |
|
|
| 61 |
16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8 |
15. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8 |
| 62 |
input, it could crash or give wrong results if characters with values |
input, it could crash or give wrong results if characters with values |
| 63 |
greater than 0xc0 were present in the subject string. (Detail: it assumed |
greater than 0xc0 were present in the subject string. (Detail: it assumed |
| 64 |
UTF-8 input when processing these items.) |
UTF-8 input when processing these items.) |
| 65 |
|
|
| 66 |
17. Added a lot of (int) casts to avoid compiler warnings in systems where |
16. Added a lot of (int) casts to avoid compiler warnings in systems where |
| 67 |
size_t is 64-bit. |
size_t is 64-bit (#991). |
| 68 |
|
|
| 69 |
18. Added a check for running out of memory when PCRE is compiled with |
17. Added a check for running out of memory when PCRE is compiled with |
| 70 |
--disable-stack-for-recursion. |
--disable-stack-for-recursion (#990). |
| 71 |
|
|
| 72 |
|
|
| 73 |
|
|
| 74 |
Version 8.02 19-Mar-2010 |
Version 8.02 19-Mar-2010 |