| 164 |
.sp |
.sp |
| 165 |
to the \fBconfigure\fP command. With this configuration, PCRE will use the |
to the \fBconfigure\fP command. With this configuration, PCRE will use the |
| 166 |
\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory |
\fBpcre_stack_malloc\fP and \fBpcre_stack_free\fP variables to call memory |
| 167 |
management functions. Separate functions are provided because the usage is very |
management functions. By default these point to \fBmalloc()\fP and |
| 168 |
predictable: the block sizes requested are always the same, and the blocks are |
\fBfree()\fP, but you can replace the pointers so that your own functions are |
| 169 |
always freed in reverse order. A calling program might be able to implement |
used. |
| 170 |
optimized functions that perform better than the standard \fBmalloc()\fP and |
.P |
| 171 |
\fBfree()\fP functions. PCRE runs noticeably more slowly when built in this |
Separate functions are provided rather than using \fBpcre_malloc\fP and |
| 172 |
way. This option affects only the \fBpcre_exec()\fP function; it is not |
\fBpcre_free\fP because the usage is very predictable: the block sizes |
| 173 |
relevant for the the \fBpcre_dfa_exec()\fP function. |
requested are always the same, and the blocks are always freed in reverse |
| 174 |
|
order. A calling program might be able to implement optimized functions that |
| 175 |
|
perform better than \fBmalloc()\fP and \fBfree()\fP. PCRE runs noticeably more |
| 176 |
|
slowly when built in this way. This option affects only the \fBpcre_exec()\fP |
| 177 |
|
function; it is not relevant for the the \fBpcre_dfa_exec()\fP function. |
| 178 |
. |
. |
| 179 |
.SH "LIMITING PCRE RESOURCE USAGE" |
.SH "LIMITING PCRE RESOURCE USAGE" |
| 180 |
.rs |
.rs |
| 258 |
.rs |
.rs |
| 259 |
.sp |
.sp |
| 260 |
.nf |
.nf |
| 261 |
Last updated: 16 April 2007 |
Last updated: 05 June 2007 |
| 262 |
Copyright (c) 1997-2007 University of Cambridge. |
Copyright (c) 1997-2007 University of Cambridge. |
| 263 |
.fi |
.fi |