Re: Inheritable configuration options.... but with default values? (updated)

I can spot at least two issues:

You can't inherit private (sic) vars, swap my with our for package vars in the base definition
you are doing a re-init which will overwrite old config

you most likely want either

local $cfg{on_error} = "warn";

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

(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",
      );
[download]

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++

Comment on Re: Inheritable configuration options.... but with default values? (updated) Select or Download Code

Replies are listed 'Best First'.
Re^2: Inheritable configuration options.... but with default values? (updated) by swl (Prior) on Feb 20, 2020 at 20:57 UTC
This order of hash entries will mean the global values override the local. It should be: `my %cfg=( %base::cfg, on_error => "warn", );` [download]	[reply] [d/l]
Re^3: Inheritable configuration options.... but with default values? (updated) by LanX (Saint) on Feb 20, 2020 at 21:57 UTC
Of course you are totally right. I was probably too occupied puzzling about the intended semantics. Fixed! Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]