| 54 |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
setting up an incorrect bitmap of starting bytes, but fortunately it could |
| 55 |
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 |
| 56 |
added property types that matched character-matching opcodes). |
added property types that matched character-matching opcodes). |
| 57 |
|
|
| 58 |
|
14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of |
| 59 |
|
possible starting bytes for non-anchored patterns. |
| 60 |
|
|
| 61 |
|
15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes |
| 62 |
|
\R, and also a number of cases that involve Unicode properties, both |
| 63 |
|
explicit and implicit when PCRE_UCP is set. |
| 64 |
|
|
| 65 |
|
16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8 |
| 66 |
|
input, it could crash or give wrong results if characters with values |
| 67 |
|
greater than 0xc0 were present in the subject string. (Detail: it assumed |
| 68 |
|
UTF-8 input when processing these items.) |
| 69 |
|
|
| 70 |
|
17. Added a lot of (int) casts to avoid compiler warnings in systems where |
| 71 |
|
size_t is 64-bit. |
| 72 |
|
|
| 73 |
|
18. Added a check for running out of memory when PCRE is compiled with |
| 74 |
|
--disable-stack-for-recursion. |
| 75 |
|
|
| 76 |
|
|
| 77 |
|
|
| 78 |
Version 8.02 19-Mar-2010 |
Version 8.02 19-Mar-2010 |
Parent Directory
| 
Revision Log
| 
Patch