/[pcre]/code/trunk/doc/pcrebuild.3
ViewVC logotype

Diff of /code/trunk/doc/pcrebuild.3

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 149 by ph10, Mon Apr 16 15:28:08 2007 UTC revision 195 by ph10, Mon Jul 30 13:23:28 2007 UTC
# Line 164  build a version of PCRE that works this Line 164  build a version of PCRE that works this
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
# Line 225  hand".) Line 229  hand".)
229  .rs  .rs
230  .sp  .sp
231  PCRE assumes by default that it will run in an environment where the character  PCRE assumes by default that it will run in an environment where the character
232  code is ASCII (or Unicode, which is a superset of ASCII). PCRE can, however, be  code is ASCII (or Unicode, which is a superset of ASCII). This is the case for
233  compiled to run in an EBCDIC environment by adding  most computer operating systems. PCRE can, however, be compiled to run in an
234    EBCDIC environment by adding
235  .sp  .sp
236    --enable-ebcdic    --enable-ebcdic
237  .sp  .sp
238  to the \fBconfigure\fP command. This setting implies  to the \fBconfigure\fP command. This setting implies
239  --enable-rebuild-chartables.  --enable-rebuild-chartables. You should only use it if you know that you are in
240    an EBCDIC environment (for example, an IBM mainframe operating system).
241  .  .
242  .  .
243  .SH "SEE ALSO"  .SH "SEE ALSO"
# Line 254  Cambridge CB2 3QH, England. Line 260  Cambridge CB2 3QH, England.
260  .rs  .rs
261  .sp  .sp
262  .nf  .nf
263  Last updated: 16 April 2007  Last updated: 30 July 2007
264  Copyright (c) 1997-2007 University of Cambridge.  Copyright (c) 1997-2007 University of Cambridge.
265  .fi  .fi

Legend:
Removed from v.149  
changed lines
  Added in v.195

  ViewVC Help
Powered by ViewVC 1.1.5