Re^3: Not inheriting imported subs

"... the poor man's solution..."

Easy said. I didn't overlook what you said. But the construct mentioned is a little bit different. And simplicity is one of the hardest things to accomplish.

"... one doesn't want to always call only fully::qualified::subs()."

Why not if these bloody details are hidden in some role?

Best regards, Karl

ŤThe Crux of the Biscuit is the Apostropheť

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

Comment on Re^3: Not inheriting imported subs Download Code

Replies are listed 'Best First'.
Re^4: Not inheriting imported subs by LanX (Saint) on Apr 29, 2019 at 16:04 UTC
Because there are many, and not every oop module is a role. As I wrote > > > Apart from the extra clutter this is not practicable with all modules. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^5: Not inheriting imported subs by karlgoethebier (Abbot) on Apr 29, 2019 at 17:48 UTC
"... not practicable with all modules." I don't give up so easily. I doubt this. Can you name any serious module (OO/Classical) where this simple approach doesn't work? Irrelevant crap etc. doesn't count. And i can't see any cluttering - at least for the moment. But i'm flexible and teachable. ŤThe Crux of the Biscuit is the Apostropheť `perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'`Help	[reply] [d/l]