Yes, this is the second option presented in OOP that I
mentioned. :)
However, as Damian Conway writes (and as you note), calling
AUTOLOAD when you mean DESTROY, and when you *know*
what you want to do with DESTROY, is less efficient than just
defining an empty DESTROY method with
sub DESTROY { }
As for ease of maintenance, I would make the case that it is just
as easy to maintain an empty method stub as a special case
in AUTOLOAD, if not easier. And it is certainly clearer when
looking at the code: rather than destruction behavior being
buried in the definition of an AUTOLOAD, you have a defined
DESTROY method to show that there is, in effect, no special
destruction code.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.