in reply to Re^4: Exporter. Correct way to override import? (archaic perldoc)
in thread Exporter. Correct way to override import?

Well, I tried to do it without the ISA. But with the serious hack that I am trying to make as an experiment I can't get around just using export_to_level. export_to_level is not exported by Exporter by the way. The goto breaks the import method that I made because of its recursive nature and so I fully depend on export_to_level. I have not been able to figure out yet how to use the function without the ISA. Also Exporter->export_to_level( 1, @_ ) ; does not seem to work for me. Errors are of the kind: <Function Name> is not exported by the Exporter module.

Replies are listed 'Best First'.
Re^6: Exporter. Correct way to override import?
by LanX (Saint) on May 06, 2018 at 21:41 UTC
    Please explain:
    • What is your goal?
    • What do you want to do in your own import()?
    • Why do you need Exporter if you want to write your own import()?

    ->export_to_level can't be "exported", since it is a method. (expects the obj/class as first argument). In order to work you need to require or use exporter first.

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

      Oh, I was just trying to abuse the Exporter to to create a flexible function importer over packages with the ability to be able to redefine the function on a higher level

      Let's say I have a package structure (where I make sure that the sub packages have a 'use parent' statement)

      Parent->ChildX ->ChildY->GrandchildYX ->GrandchildYY

      Inside of these packages I want have a bunch of functions with the same name:

      Parent.function1 (function1 defined in Parent) ChildX.function1 (function1 imported from Parent) ChildX.function2 (function2 defined in ChildX) ChildY.function1 (function1 defined in ChildY) ChildY.function2 (function2 defined in ChildY) GrandchildYX.function1 (function1 imported from ChildY) GrandchildYX.function2 (function2 defined in GrandchildYX)
      Any program that I use
      use Parent qw(function1) # function 1 from Parent or use ChildX qw(function1 function2) # function1 from Parent, function2 +from ChildX or use ChildY qw(function1) # function1 from ChildY or use GrandchildYX qw(function1 function2) # function1 from ChildY, func +tion2 from GrandchildYX

      The experiment/challenge was to see if I can pull this off by writing ONE import function in Parent

      The code that I wrote works now I think, but it relies on the method export_to_level which I basically abuse and call static

      If you want I can share the code (not now though it is late), but I have to warn you it is an ugly piece

        not sure if I understand what you describe, but
        package myModule; require XYZ; sub import { XYZ->import("function") } 1;

        should import XYZ::function if you use MyModule

        update

        Sorry seems only to work for pragmas ... the code in Modern::Perl is confusing me...

        update
        you can always do it manually

        package myModule; use strict; use warnings; require Data::Dump; sub import { my $target_pkg = (caller)[0]; no strict 'refs'; for my $func ( qw/dd pp/) { *{"$target_pkg::$func"}= \&{"Data::Dump::$func"}; } } 1;

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