From: Jerry Hedden Date: Thu, 12 Oct 2006 07:47:37 +0000 (-0700) Subject: threads::shared 1.04 X-Git-Tag: accepted/trunk/20130322.191538~16872 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7446b2eb9aec0607a1f998085f2e7dc809540822;p=platform%2Fupstream%2Fperl.git threads::shared 1.04 Message-ID: <20061012144737.56305.qmail@web30207.mail.mud.yahoo.com> p4raw-id: //depot/perl@29003 --- diff --git a/ext/threads/shared/shared.pm b/ext/threads/shared/shared.pm index 4ab12db..c2595f2 100644 --- a/ext/threads/shared/shared.pm +++ b/ext/threads/shared/shared.pm @@ -5,7 +5,7 @@ use 5.008; use strict; use warnings; -our $VERSION = '1.03'; +our $VERSION = '1.04'; my $XS_VERSION = $VERSION; $VERSION = eval $VERSION; @@ -73,7 +73,7 @@ threads::shared - Perl extension for sharing data structures between threads =head1 VERSION -This document describes threads::shared version 1.03 +This document describes threads::shared version 1.04 =head1 SYNOPSIS @@ -345,7 +345,8 @@ It is often not wise to share an object unless the class itself has been written to support sharing. For example, an object's destructor may get called multiple times, one for each thread's scope exit. Another example, is that the contents of hash-based objects will be lost due to the above mentioned -limitation. +limitation. See F (in the CPAN distribution of this +module) for how to create a class that supports object sharing. Does not support C on arrays! @@ -367,7 +368,7 @@ L Discussion Forum on CPAN: L Annotated POD for L: -L +L L, L