Consider passing what you call "the parent" around to each object that implements an action? So far you've been somewhat unclear about what you actually need, so it is somewhat hard to come up with good names for the parts that make sense in your context.

Maybe using "configuration" as name for what you call "parent" and "action" as name for what you call "child" would help?

my $cfg = My::Config->new_from_file('nysus.yml');
$cfg->process( $myfile );

package My::Config;
use Module::Pluggable require => '1',
                      sub_name => 'actions',
                      instantiate => 'new',
                      ;

sub My::Config::process( $self, $filename ) {
    for my $action ($self->actions) {
        $action->operate( $self, $filename );
    };
};

[download]

I don't think that passing data around in $self should be an overarching design principle.

Most of the code above is from Module::Pluggable, which still feels very applicable from what you've described so far and from the problems you encounter.

Maybe if you can elaborate more on the concrete problem you're trying to solve and the problems you encounter, we can give you more concrete advice?

In reply to Re^6: Creating dynamic parent/child relationships by Corion
in thread Creating dynamic parent/child relationships by nysus

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.