I can spot at least two issues:

you most likely want either

local $cfg{on_error} = "warn";

or

my %cfg=( # now my to avoid overwriting any glob +al %cfg %cfg, # inherited defaults * on_error => "warn", );

(untested)

edit

and in the second case you won't even need inheritance because with pkg-vars you can be explicit

my %cfg=( # now my to avoid overwriting any glob +al %cfg %base::cfg, # inherited defaults * on_error => "warn", );

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

update

added local and my

update

There are more options ... but the expected behavior is not clear to me ...

To answer this properly we'd need to see an SSCCE

update

*) fixed error in order, swl++


In reply to Re: Inheritable configuration options.... but with default values? (updated) by LanX
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.