--- code/trunk/ChangeLog	2010/05/23 18:48:54	523
+++ code/trunk/ChangeLog	2010/06/01 16:21:42	532
@@ -54,7 +54,25 @@
     setting up an incorrect bitmap of starting bytes, but fortunately it could 
     not have actually happened in practice until change 8 above was made (it 
     added property types that matched character-matching opcodes).
- 
+    
+14. pcre_study() now recognizes \h, \v, and \R when constructing a bit map of 
+    possible starting bytes for non-anchored patterns. 
+    
+15. Extended the "auto-possessify" feature of pcre_compile(). It now recognizes
+    \R, and also a number of cases that involve Unicode properties, both 
+    explicit and implicit when PCRE_UCP is set.
+
+16. If a repeated Unicode property match (e.g. \p{Lu}*) was used with non-UTF-8
+    input, it could crash or give wrong results if characters with values 
+    greater than 0xc0 were present in the subject string. (Detail: it assumed 
+    UTF-8 input when processing these items.)
+    
+17. Added a lot of (int) casts to avoid compiler warnings in systems where
+    size_t is 64-bit.
+    
+18. Added a check for running out of memory when PCRE is compiled with
+    --disable-stack-for-recursion. 
+    
 
 
 Version 8.02 19-Mar-2010