Re: Shared object destruction: docs and historical behavior

2013-06-24 Thread Dave Mitchell
On Mon, Jun 24, 2013 at 08:30:32AM -0500, Mike Pomraning wrote: > On Mon, Jun 24, 2013 at 5:53 AM, Dave Mitchell wrote: > > On Sat, Jun 22, 2013 at 11:26:41AM -0500, Mike Pomraning wrote: > >> The threads::shared POD warns: > >> > >> [A shared] object's destructor may get called multiple times

Re: Shared object destruction: docs and historical behavior

2013-06-24 Thread Mike Pomraning
On Mon, Jun 24, 2013 at 5:53 AM, Dave Mitchell wrote: > On Sat, Jun 22, 2013 at 11:26:41AM -0500, Mike Pomraning wrote: >> The threads::shared POD warns: >> >> [A shared] object's destructor may get called multiple times, once >> for each thread's scope exit. >> >> Is this caution still accura

Re: Shared object destruction: docs and historical behavior

2013-06-24 Thread Elizabeth Mattijsen
On Jun 24, 2013, at 12:53 PM, Dave Mitchell wrote: > On Sat, Jun 22, 2013 at 11:26:41AM -0500, Mike Pomraning wrote: >> The threads::shared POD warns: >> >>[A shared] object's destructor may get called multiple times, once >> for each thread's scope exit. >> >> Is this caution still accurate

Re: Shared object destruction: docs and historical behavior

2013-06-24 Thread Dave Mitchell
On Sat, Jun 22, 2013 at 11:26:41AM -0500, Mike Pomraning wrote: > The threads::shared POD warns: > > [A shared] object's destructor may get called multiple times, once > for each thread's scope exit. > > Is this caution still accurate? > > Beginning with perl 5.8.9 / threads 1.71 / threads::

Re: Shared object destruction: docs and historical behavior

2013-06-22 Thread Elizabeth Mattijsen
On Jun 22, 2013, at 6:26 PM, Mike Pomraning wrote: > The threads::shared POD warns: > > [A shared] object's destructor may get called multiple times, once > for each thread's scope exit. FWIW, that's exactly the reason I once create Thread::Bless. > Is this caution still accurate? I have no