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:
Any program that I useParent.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)
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
In reply to Re^7: Exporter. Correct way to override import?
by Veltro
in thread Exporter. Correct way to override import?
by Veltro
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |