Yes, that is true: the solution relies on having the subclasses at least to execute the parent class DESTROY method though SUPER. Using DESTROY was my best bet because of classes like Class::Accessor that creates code during execution phase. Honestly, I don't know if CHECK and/or END blocks manipulation will not broke code generators more than using DESTROY method...
But iterating all over packages looking for methods that were not override looks like a bit overkill, since the parent class already knows which abstract methods it has. Anyway, how would you do it? I mean, how to mark an method as abstract? Or do you mean to really start checking every package for a "@abstract_methods" (or anything else) available as an indication this class must be checked?
Alceu Rodrigues de Freitas Junior
---------------------------------
"You have enemies? Good. That means you've stood up for something, sometime in your life." - Sir Winston Churchill
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.