(I was only using __PACKAGE__ to see why things weren't being put in the right namespace.)
The sub Mod::foo { } suggestion was a new thought, but like __PACKAGE__, the magic identifier SUPER was not correct. I would rather use SUPER than hardwire the base class, but it's pretty arbitrary.
As for the many suggestions to rethink the design; yes, it's a good idea to rethink it. However, I've rethought, and in my particular case, it rightfully should be one class with a few semi-distinct duties that are not easy to aggregate or embed or delegate. I'm working near the base of a large class hierarchy, and the base classes really must cover their core duties.
--
[ e d @ h a l l e y . c c ]
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.