Or you could use multiple inheritance: e.g. our @ISA=qw(A B). Is there a reason that you are using Mixin instead of multiple inheritance or did it just happen that way?
I don't generally recommend multiple inheritance because weird things can happen if method names aren't orthogonal and you try to get one class hierarchy to define methods that override same named methods in another class hierarchy (e.g. the "diamond inheritance problem"). However, in your case method name clashes doesn't seem to be an issue as you have no concerns importing them into your namespace. If subroutine syntax is an alternative then I would presume your mixin classes are flat as well.
Best, beth
-
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.
|