--- code/trunk/ChangeLog	2009/03/01 14:13:34	378
+++ code/trunk/ChangeLog	2009/03/02 20:30:05	379
@@ -31,6 +31,11 @@
 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.
       
 
 Version 7.8 05-Sep-08