Hi Monks,

I have a question about designing Moose classes: I have a module A which has multiple features B, C, D, because multiple people will work on these and it would be nice to have this logical separation of the different features. The features B, C, D need to have access to A themselves (they run something on A).

I want to put A, B, C, D, ... into different files.

The user should only have to instantiate A and then use the other classes through it, such as: 

my $a = A->new();
$a->b->method();
$a->c->another_method();

[download]
A simple way to make this work would be: 
package A;
has b => ( isa => 'B' );
has c => ( isa => 'C' );
sub BUILD {
    my ($self) = @_;
    $self->b(B->new(a => $self));
    $self->c(C->new(a => $self));
}

package B;
has a => ( isa => 'A', required => 1);
sub method { 
   my ($self) = @_;
   $self->a->exec(...); # Stuff related to B
}

package C;
has a => ( isa => 'A', required => 1);
sub another_method {
    my ($self) = @_;
    $self->a->exec(...); # Stuff related to C
}

[download]

But this solution doesn't seem to be very 'clean' apart from that it does what it should. It's not making use of any OO concepts, it's just hardcoding the different classes together.

I'm not very familiar with Moose Roles, could I use those to achieve the desired behavior?

In reply to Moose design question by elTriberium

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.