Re: Config::General inheritance

Well, I just stumbled into it.

I was a bit blinded by this ExtendedAccess parameter doo-dad. I just discovered that if I:

use base qw (Config::General::Extended);
[download]

yet still call new on Config::General, I get the desired result.

Corion was trying to tell me that; and when I finally paid attention, it was obvious.

Thanks for reading along... :)

Comment on Re: Config::General inheritance Download Code

Replies are listed 'Best First'.
Re^2: Config::General inheritance by fbicknel (Beadle) on Feb 25, 2011 at 20:12 UTC
Well now. I even have replicated how I wound up going down that primrose path. When I went back to my production code, I found in my inheriting module; after applying the revelation I talked out in this forum: `use base qw (Config::General::Extended); sub new { ... my $self = new SUPER::new ( ...` [download] Which of course executes C::G::Extended->new... and that's a bad thing. Instead of changing SUPER to Config::General, as I should have, I changed the use base line. Ah. So that's what happened.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Config::General inheritance
by fbicknel (Beadle) on Feb 25, 2011 at 20:12 UTC

ing

use base qw (Config::General::Extended);
sub new {
...
  my $self = new SUPER::new (
...
[download]

use base

[reply]
[d/l]