Hi, I would use Moo for all your object creation needs if I were you. 

package MyBase {
    use Moo;

    has cfg => (
        is      => 'rw',
        default => sub {
            return { on_error => 'exit', output_type => 'text' };
        },
    );
};

package MyChild {
    use Moo;
    extends 'MyBase';

    sub BUILD {
        shift->cfg->{on_error} = 'warn';
    }
};

use strict;
use warnings;
use MyChild;

use Test::More;

ok( my $obj = MyChild->new );
is_deeply( $obj->cfg, { on_error => 'warn', output_type => 'text' } );

done_testing;

[download]

Hope this helps!


The way forward always starts with a minimal test.

In reply to Re: Inheritable configuration options.... but with default values? by 1nickt
in thread Inheritable configuration options.... but with default values? by Amblikai

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.