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

In reply to Re: How to write a Mixin without Exporter mess? by ELISHEVA
in thread How to write a Mixin without Exporter mess? by saintmike

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.