83 |
makes it run a lot more slowly, however. Details of how to do this are given in |
makes it run a lot more slowly, however. Details of how to do this are given in |
84 |
the |
the |
85 |
<a href="pcrebuild.html"><b>pcrebuild</b></a> |
<a href="pcrebuild.html"><b>pcrebuild</b></a> |
86 |
documentation. |
documentation. When built in this way, instead of using the stack, PCRE obtains |
87 |
|
and frees memory by calling the functions that are pointed to by the |
88 |
|
<b>pcre_stack_malloc</b> and <b>pcre_stack_free</b> variables. By default, these |
89 |
|
point to <b>malloc()</b> and <b>free()</b>, but you can replace the pointers to |
90 |
|
cause PCRE to use your own functions. Since the block sizes are always the |
91 |
|
same, and are always freed in reverse order, it may be possible to implement |
92 |
|
customized memory handlers that are more efficient than the standard functions. |
93 |
</P> |
</P> |
94 |
<P> |
<P> |
95 |
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 |
145 |
REVISION |
REVISION |
146 |
</b><br> |
</b><br> |
147 |
<P> |
<P> |
148 |
Last updated: 12 March 2007 |
Last updated: 05 June 2007 |
149 |
<br> |
<br> |
150 |
Copyright © 1997-2007 University of Cambridge. |
Copyright © 1997-2007 University of Cambridge. |
151 |
<br> |
<br> |