I was studying your examples again and came up with another question. Suppose I take your My/Bar.pm file and copy it as-is to a new file My/Xyzzy.pm. Now suppose I create a new file xyzzy_version_test.pl to reference and use this new module as follows:
#!/tool/bin/perl -w use strict; use lib '/home/user/perl_modules/lib/perl5/My'; use Xyzzy; say_it();
Now the package name matches the file name. Running this code gives the following error:
Undefined subroutine &main::say_it called at ./xyzzy_version_test.pl l +ine 6.
It seems that the package name Xyzzy is still explicitly required in this case to call the say_it function even though the package name now matches the filename. After doing some searching, I found that adding the following to My/Xyzzy.pm allows the above call to say_it() (without the Xyzzy->) to work:
use Exporter qw(import); our @EXPORT = qw(say_it); our @EXPORT_OK = qw();
My question is: are the above 3 lines of code that I added to My/Xyzzy.pm (and using qw() to reference specific subroutines in a package, e.g. use Xyzzy qw(say_it);, had I included say_it in the EXPORT_OK list rather than the EXPORT list) only used to prevent the user from having to prefix every call to a exported subroutine with Package-> every time, or do they serve other purposes?
In reply to Re^4: help with versioning modules
by Special_K
in thread help with versioning modules
by Special_K
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |