in reply to Not inheriting imported subs

"...What am I missing?..."

I guess you miss nothing. But don't you want a kind of proxy? I'm not sure if this is really helpful and if i understood you right - and sometimes my mind is a bit free-floating.

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

Replies are listed 'Best First'.
Re^2: Not inheriting imported subs
by LanX (Saint) on Apr 29, 2019 at 14:13 UTC
    no, I already mentioned the poor man's solution you got in that thread. (which is appropriate in that case)

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

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

      "... 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

        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