Hi, I have this strange question while doing some multi-threaded programming.

The code below output : 

thread start
Destroy A=HASH(0x10124254)
thread start
Destroy A=HASH(0x101254f4)
Destroy A=HASH(0x1002f054)

[download]
with two more DESTROY calls, how can I avoid them? I am using ActiveState 5.8.4 810 on Win XP

Also, if I use  my $a : shared = A->new() then there will be another two more DESTROY calls. 

use threads;
use threads::shared;
{
    package A;
    use threads;
    use threads::shared;
    sub new {
        my $class = shift;
        my $self = &share({});
        return bless $self, $class;
    }
    sub get_s {
    }
    sub DESTROY {
        print "Destroy $_[0]\n";
    }
}

my $a  = &share(A->new());
for (1..2) {
    async {
        print "thread start\n";
        $a->get_s();
    }->join();
}

[download]
Thanks.

In reply to How to avoid extra DESTROY calls in multi-threaded program? by jwu

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.