You won't get memory leaks per se, but you may sometimes get tripped by the somewhat random order of destruction in final cleanup.

This usually only makes a difference if your class data includes objects that have a DESTROY method, eg:

sub DESTROY { my $self = shift; $self->{dbh}->disconnect if $self->{connected}; }

In that example, during global destruction it is possible that $self->{dbh} has been destroyed before this object, in which case you'd get an error in that DESTROY.

I often get around that problem with a simple:

my $class_data; END { $class_data = undef }
.. which help to ensure things will be tidied up in an appropriate order by removing the need for perl to guess at a sensible order to destroy things.

Hugo


In reply to Re: "our" versus "my" for class data by hv
in thread "our" versus "my" for class data by mp

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.