--- code/trunk/doc/pcrestack.3	2007/03/12 15:10:25	122
+++ code/trunk/doc/pcrestack.3	2007/06/05 11:38:06	174
@@ -72,7 +72,13 @@
 .\" HREF
 \fBpcrebuild\fP
 .\"
-documentation.
+documentation. When built in this way, instead of using the stack, PCRE obtains
+and frees memory by calling the functions that are pointed to by the
+\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables. By default, these
+point to \fBmalloc()\fP and \fBfree()\fP, but you can replace the pointers to
+cause PCRE to use your own functions. Since the block sizes are always the 
+same, and are always freed in reverse order, it may be possible to implement 
+customized memory handlers that are more efficient than the standard functions.
 .P
 In Unix-like environments, there is not often a problem with the stack unless
 very long strings are involved, though the default limit on stack size varies
@@ -129,6 +135,6 @@
 .rs
 .sp
 .nf
-Last updated: 12 March 2007
+Last updated: 05 June 2007
 Copyright (c) 1997-2007 University of Cambridge.
 .fi