--- code/trunk/ChangeLog	2008/08/25 18:28:05	371
+++ code/trunk/ChangeLog	2009/03/17 21:16:01	391
@@ -1,7 +1,71 @@
 ChangeLog for PCRE
 ------------------
 
-Version 7.8 25-Aug-08
+Version 7.9 xx-xxx-09
+---------------------
+
+1.  When building with support for bzlib/zlib (pcregrep) and/or readline 
+    (pcretest), all targets were linked against these libraries. This included
+    libpcre, libpcreposix, and libpcrecpp, even though they do not use these
+    libraries. This caused unwanted dependencies to be created. This problem
+    has been fixed, and now only pcregrep is linked with bzlib/zlib and only 
+    pcretest is linked with readline.
+    
+2.  The "typedef int BOOL" in pcre_internal.h that was included inside the
+    "#ifndef FALSE" condition by an earlier change (probably 7.8/18) has been
+    moved outside it again, because FALSE and TRUE are already defined in AIX,
+    but BOOL is not.
+    
+3.  The pcre_config() function was treating the PCRE_MATCH_LIMIT and 
+    PCRE_MATCH_LIMIT_RETURSION values as ints, when they should be long ints.
+    
+4.  The pcregrep documentation said spaces were inserted as well as colons (or
+    hyphens) following file names and line numbers when outputting matching
+    lines. This is not true; no spaces are inserted. I have also clarified the 
+    wording for the --colour (or --color) option.
+    
+5.  In pcregrep, when --colour was used with -o, the list of matching strings
+    was not coloured; this is different to GNU grep, so I have changed it to be
+    the same.
+    
+6.  When --colo(u)r was used in pcregrep, only the first matching substring in
+    each matching line was coloured. Now it goes on to look for further matches 
+    of any of the test patterns, which is the same behaviour as GNU grep.  
+    
+7.  A pattern that could match an empty string could cause pcregrep to loop; it 
+    doesn't make sense to accept an empty string match in pcregrep, so I have 
+    locked it out (using PCRE's PCRE_NOTEMPTY option). By experiment, this
+    seems to be how GNU grep behaves.
+    
+8.  The pattern (?(?=.*b)b|^) was incorrectly compiled as "match must be at
+    start or after a newline", because the conditional assertion was not being 
+    correctly handled. The rule now is that both the assertion and what follows 
+    in the first alternative must satisfy the test. 
+    
+9.  If auto-callout was enabled in a pattern with a conditional group, PCRE 
+    could crash during matching.
+    
+10. The PCRE_DOLLAR_ENDONLY option was not working when pcre_dfa_exec() was 
+    used for matching. 
+    
+11. Unicode property support in character classes was not working for 
+    characters (bytes) greater than 127 when not in UTF-8 mode.
+    
+12. Added the -M command line option to pcretest. 
+
+14. Added the non-standard REG_NOTEMPTY option to the POSIX interface.
+
+15. Added the PCRE_NO_START_OPTIMIZE match-time option.
+
+16. Added comments and documentation about mis-use of no_arg in the C++ 
+    wrapper.
+    
+17. Implemented support for UTF-8 encoding in EBCDIC environments, a patch
+    from Martin Jerabek that uses macro names for all relevant character and 
+    string constants.
+      
+
+Version 7.8 05-Sep-08
 ---------------------
 
 1.  Replaced UCP searching code with optimized version as implemented for Ad
@@ -73,6 +137,11 @@
 
 18. Tidied a few places to stop certain compilers from issuing warnings.
 
+19. Updated the Virtual Pascal + BCC files to compile the latest v7.7, as
+    supplied by Stefan Weber. I made a further small update for 7.8 because
+    there is a change of source arrangements: the pcre_searchfuncs.c module is
+    replaced by pcre_ucd.c.
+
 
 Version 7.7 07-May-08
 ---------------------