What you have should, on the surface, be working.
:DEFAULT should be doing what it says on the tin, but try explicitly naming the subs you wish to import, and see if this works.
One point that occurs to me is that Register.pm could be switching namespaces - with further package declarations. If this is the case, the use will import the subs once - into the package namespace of its context. This is why you need to declare your package first before using Exporter style modules. OO modules don't suffer from this problem as they use a different technique for getting to the namespace.
If you've still got a problem, I suggest dumping out the key stashes (symbol table hashes) after BEGIN has happened, to see whether Exporter has aliased the subs properly. One way to do this is with the debugger (perl -d) - run it up and issue the command:
DB<1> x %Register::and see if the sub names appear.
Alternatively, add the following lines to your main program:
use Data::Dumper; print Dumper \%Register::;
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
In reply to Re^3: error for undefined function that's been imported
by rinceWind
in thread error for undefined function that's been imported
by argv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |