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
package's name-space.
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
altogether?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|