Not to flog a dead horse...
What about:
OR#tapping a locally placed file of subroutines use Mycommonroutines;
OR#using the lib command to change the @INC use lib Mycommonroutines;
#using Export to be more specific about what subs to import use Mycommonroutines qw(get_setup);
Can I assume:
1. use of lib in this case is ill-advised?
2. the advantage (only?) of the Export route is to allow specificity of what routines are imported?
In reply to Re^2: Questions about sharing code
by bradcathey
in thread Questions about sharing code
by bradcathey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |