Has the community reached a consensus on the preferred way to implement
a mixin class? After reviewing some common modules, I have come
across at least three different ways of implementing a mixin class.
- Using Standard Perl Inheritance
A class like Class::Accessor uses the Perl inheritance
mechanism to bring their methods into the package name-space. If you
want to bring in more mixin classes, you need to add them to your
use base qw(..) statement.
- Customized import And Manipulation of the Symbol Table
Unlike Class::Accessor, Class::Trigger uses a
customized import function to manipulate the package's symbol
table to add the new methods.
- Export methods into Package Name-Space
Finally, a module like Class::DBI::FromCGI uses
Exporter to export the method names directly into the
There may be other ways of implementing a mixin class. Are any of the
methods listed above the preferred way, or is there another method
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||