summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorJerry D. Hedden <jdhedden@cpan.org>2007-02-12 04:04:33 -0800
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-02-15 09:34:01 +0000
commit878090d5582120ef9336936d4fc06895b4fd242a (patch)
treeb937d124e5c21f6581ac096678f212c38b29f246 /pod
parente9950d3b0610b91bb9d19cb0918fe7e81505fd79 (diff)
downloadperl-878090d5582120ef9336936d4fc06895b4fd242a.tar.gz
Use newer 'threads' constructs
From: "Jerry D. Hedden" <jdhedden@yahoo.com> Message-ID: <844555.64815.qm@web30202.mail.mud.yahoo.com> p4raw-id: //depot/perl@30310
Diffstat (limited to 'pod')
-rw-r--r--pod/perlapi.pod2
-rw-r--r--pod/perlxs.pod2
2 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlapi.pod b/pod/perlapi.pod
index b8687945af..4ebc353db1 100644
--- a/pod/perlapi.pod
+++ b/pod/perlapi.pod
@@ -610,7 +610,7 @@ without it we only clone the data and zero the stacks,
with it we copy the stacks and the new perl interpreter is
ready to run at the exact same point as the previous one.
The pseudo-fork code uses COPY_STACKS while the
-threads->new doesn't.
+threads->create doesn't.
CLONEf_KEEP_PTR_TABLE
perl_clone keeps a ptr_table with the pointer of the old
diff --git a/pod/perlxs.pod b/pod/perlxs.pod
index 6d14bae275..61e023f3a6 100644
--- a/pod/perlxs.pod
+++ b/pod/perlxs.pod
@@ -2007,7 +2007,7 @@ comma, i.e. C<_aMY_CXT>, C<aMY_CXT_>, C<_pMY_CXT> and C<pMY_CXT_>.
=item MY_CXT_CLONE
By default, when a new interpreter is created as a copy of an existing one
-(eg via C<<threads->new()>>), both interpreters share the same physical
+(eg via C<<threads->create()>>), both interpreters share the same physical
my_cxt_t structure. Calling C<MY_CXT_CLONE> (typically via the package's
C<CLONE()> function), causes a byte-for-byte copy of the structure to be
taken, and any future dMY_CXT will cause the copy to be accessed instead.