summaryrefslogtreecommitdiff
path: root/doc/pcre2_jit_stack_assign.3
diff options
context:
space:
mode:
authorMatthew Vernon <matthew@debian.org>2018-10-26 19:26:32 +0100
committerMatthew Vernon <matthew@debian.org>2018-10-26 19:26:32 +0100
commit1cab70503159c32de523a1762614b6829687a116 (patch)
tree26068f08ea492a5d12216d014a1a58372c12d360 /doc/pcre2_jit_stack_assign.3
parent39c4b070d68976779cdb3f2a9f886de962870a37 (diff)
parentb03dbaae48971b62fe6ce174a8dfbbcaf1314d7e (diff)
Merge tag '10.32'
Upstream version 10.32
Diffstat (limited to 'doc/pcre2_jit_stack_assign.3')
-rw-r--r--doc/pcre2_jit_stack_assign.312
1 files changed, 8 insertions, 4 deletions
diff --git a/doc/pcre2_jit_stack_assign.3 b/doc/pcre2_jit_stack_assign.3
index 66b8095..33d2e1c 100644
--- a/doc/pcre2_jit_stack_assign.3
+++ b/doc/pcre2_jit_stack_assign.3
@@ -1,4 +1,4 @@
-.TH PCRE2_JIT_STACK_ASSIGN 3 "08 November 2014" "PCRE2 10.0"
+.TH PCRE2_JIT_STACK_ASSIGN 3 "28 June 2018" "PCRE2 10.32"
.SH NAME
PCRE2 - Perl-compatible regular expressions (revised API)
.SH SYNOPSIS
@@ -24,7 +24,10 @@ passed to a matching function. The arguments of this function are:
callback a callback function
callback_data a JIT stack or a value to be passed to the callback
.P
-If \fIcallback\fP is NULL and \fIcallback_data\fP is NULL, an internal 32K
+If \fImcontext\fP is NULL, the function returns immediately, without doing
+anything.
+.P
+If \fIcallback\fP is NULL and \fIcallback_data\fP is NULL, an internal 32KiB
block on the machine stack is used.
.P
If \fIcallback\fP is NULL and \fIcallback_data\fP is not NULL,
@@ -33,8 +36,9 @@ If \fIcallback\fP is NULL and \fIcallback_data\fP is not NULL,
.P
If \fIcallback\fP not NULL, it is called with \fIcallback_data\fP as an
argument at the start of matching, in order to set up a JIT stack. If the
-result is NULL, the internal 32K stack is used; otherwise the return value must
-be a valid JIT stack, the result of calling \fBpcre2_jit_stack_create()\fP.
+result is NULL, the internal 32KiB stack is used; otherwise the return value
+must be a valid JIT stack, the result of calling
+\fBpcre2_jit_stack_create()\fP.
.P
You may safely use the same JIT stack for multiple patterns, as long as they
are all matched in the same thread. In a multithread application, each thread