72 |
.\" HREF |
.\" HREF |
73 |
\fBpcrebuild\fP |
\fBpcrebuild\fP |
74 |
.\" |
.\" |
75 |
documentation. |
documentation. When built in this way, instead of using the stack, PCRE obtains |
76 |
|
and frees memory by calling the functions that are pointed to by the |
77 |
|
\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables. By default, these |
78 |
|
point to \fBmalloc()\fP and \fBfree()\fP, but you can replace the pointers to |
79 |
|
cause PCRE to use your own functions. Since the block sizes are always the |
80 |
|
same, and are always freed in reverse order, it may be possible to implement |
81 |
|
customized memory handlers that are more efficient than the standard functions. |
82 |
.P |
.P |
83 |
In Unix-like environments, there is not often a problem with the stack unless |
In Unix-like environments, there is not often a problem with the stack unless |
84 |
very long strings are involved, though the default limit on stack size varies |
very long strings are involved, though the default limit on stack size varies |
135 |
.rs |
.rs |
136 |
.sp |
.sp |
137 |
.nf |
.nf |
138 |
Last updated: 12 March 2007 |
Last updated: 05 June 2007 |
139 |
Copyright (c) 1997-2007 University of Cambridge. |
Copyright (c) 1997-2007 University of Cambridge. |
140 |
.fi |
.fi |