--- code/trunk/ChangeLog	2010/11/03 18:32:55	566
+++ code/trunk/ChangeLog	2010/11/21 18:45:10	576
@@ -82,6 +82,44 @@
         
     (c) The pcredemo.c sample program did not have any code at all to handle
         the cases when CRLF is a valid newline sequence. 
+        
+14. Neither pcre_exec() nor pcre_dfa_exec() was checking that the value given
+    as a starting offset was within the subject string. There is now a new
+    error, PCRE_ERROR_BADOFFSET, which is returned if the starting offset is 
+    negative or greater than the length of the string. In order to test this, 
+    pcretest is extended to allow the setting of negative starting offsets.
+    
+15. In both pcre_exec() and pcre_dfa_exec() the code for checking that the 
+    starting offset points to the beginning of a UTF-8 character was 
+    unnecessarily clumsy. I tidied it up.  
+    
+16. Added PCRE_ERROR_SHORTUTF8 to make it possible to distinguish between a
+    bad UTF-8 sequence and one that is incomplete. 
+    
+17. Nobody had reported that the --include_dir option, which was added in 
+    release 7.7 should have been called --include-dir (hyphen, not underscore) 
+    for compatibility with GNU grep. I have changed it to --include-dir, but 
+    left --include_dir as an undocumented synonym, and the same for 
+    --exclude-dir, though that is not available in GNU grep, at least as of 
+    release 2.5.4. 
+    
+18. At a user's suggestion, the macros GETCHAR and friends (which pick up UTF-8 
+    characters from a string of bytes) have been redefined so as not to use
+    loops, in order to improve performance in some environments. At the same 
+    time, I abstracted some of the common code into auxiliary macros to save 
+    repetition (this should not affect the compiled code).
+    
+19. If \c was followed by a multibyte UTF-8 character, bad things happened. A 
+    compile-time error is now given if \c is not followed by an ASCII 
+    character, that is, a byte less than 128. (In EBCDIC mode, the code is 
+    different, and any byte value is allowed.)
+    
+20. Recognize (*NO_START_OPT) at the start of a pattern to set the PCRE_NO_
+    START_OPTIMIZE option, which is now allowed at compile time - but just
+    passed through to pcre_exec() or pcre_dfa_exec(). This makes it available
+    to pcregrep and other applications that have no direct access to PCRE 
+    options. The new /Y option in pcretest sets this option when calling 
+    pcre_compile().  
 
 
 Version 8.10 25-Jun-2010