summaryrefslogtreecommitdiff
path: root/pod/perlmod.pod
diff options
context:
space:
mode:
authorFlorian Ragwitz <rafl@debian.org>2010-11-29 19:37:25 +0100
committerFlorian Ragwitz <rafl@debian.org>2010-11-29 19:37:25 +0100
commitbca52ca1d767654670429383dea23f9af89ab5ea (patch)
tree75e3f2df4d9badb73d6adb4de0215f45c60abac4 /pod/perlmod.pod
parent28502098d789b49672c607a23fd42af03fab5a04 (diff)
downloadperl-bca52ca1d767654670429383dea23f9af89ab5ea.tar.gz
Fix a typo in perlmod
Diffstat (limited to 'pod/perlmod.pod')
-rw-r--r--pod/perlmod.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlmod.pod b/pod/perlmod.pod
index 90655867c9..7c5358f937 100644
--- a/pod/perlmod.pod
+++ b/pod/perlmod.pod
@@ -587,7 +587,7 @@ For example: if in the parent there are two references to a single blessed
hash, then in the child there will be two references to a single undefined
scalar value instead.
This provides a simple mechanism for making a module threadsafe; just add
-C<sub CLONE_SKIP { 1 }> at the top of the class, and C<DESTROY()> will be
+C<sub CLONE_SKIP { 1 }> at the top of the class, and C<DESTROY()> will
now only be called once per object. Of course, if the child thread needs
to make use of the objects, then a more sophisticated approach is
needed.