--- code/trunk/ChangeLog	2008/03/28 12:06:36	329
+++ code/trunk/ChangeLog	2008/04/12 15:59:03	336
@@ -10,7 +10,7 @@
     
 2.  Applied Craig's patch to pcrecpp.cc to restore ABI compatibility with
     pre-7.6 versions, which defined a global no_arg variable instead of putting
-    it in the RE class.
+    it in the RE class. (See also #8 below.)
     
 3.  Remove a line of dead code, identified by coverity and reported by Nuno 
     Lopes. 
@@ -39,7 +39,29 @@
     
 8.  Applied Craig's patch to pcrecpp.cc to fix a problem in OS X that was
     caused by fix #2  above. (Subsequently also a second patch to fix the
-    first patch.) 
+    first patch. And a third patch - this was a messy problem.) 
+    
+9.  Applied Craig's patch to remove the use of push_back(). 
+
+10. Applied Alan Lehotsky's patch to add REG_STARTEND support to the POSIX
+    matching function regexec().
+    
+11. Added support for the Oniguruma syntax \g<name>, \g<n>, \g'name', \g'n', 
+    which, however, unlike Perl's \g{...}, are subroutine calls, not back 
+    references. PCRE supports relative numbers with this syntax (I don't think
+    Oniguruma does).
+    
+12. Previously, a group with a zero repeat such as (...){0} was completely 
+    omitted from the compiled regex. However, this means that if the group
+    was called as a subroutine from elsewhere in the pattern, things went wrong
+    (an internal error was given). Such groups are now left in the compiled 
+    pattern, with a new opcode that causes them to be skipped at execution 
+    time.
+    
+13. Added the PCRE_JAVASCRIPT_COMPAT option. This currently does two things:
+    (a) A lone ] character is dis-allowed (Perl treats it as data).
+    (b) A back reference to an unmatched subpattern matches an empty string 
+        (Perl fails the current match path).
 
 
 Version 7.6 28-Jan-08