Dear colleagues,

I started using Moose about a month ago and I like it.

Now I have a situation when I have some role (let's call it Role) consumed by two classes - ClassA and ClassB. The role has a method called do_something(). This method being called as ClassA->do_something() creates a ClassB-object.

    require ClassB.pm;
    $objB = ClassB->new();

[download]

As I see by further tests, it works fine, but I'm getting warnings:

Subroutine foo redefined at /XXX/lib/YYY/ClassB.pm line 17.
Subroutine bar redefined at /XXX/lib/YYY/ClassB.pm line 23.
Subroutine baz redefined at /XXX/lib/YYY/ClassB.pm line 30.

[download]

Actually it says all methods I have in the role are redefined.

Is there a way to create a ClassB object from ClassA if both classes consume the same role?

Lots of thanks for your help!

V.Melnik

In reply to Two Moose classes consumering the same role and using each other by v_melnik

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.