Re: Recursive use causes subroutine redefinition

[ysth]

Nothing is wrong with your recursive uses; the problem is that you are also loading Foo.pm as a script, bypassing the multiple load checks that exist for require or use. The same thing happens without the recursion:

$ cat>Baz.pm
package Baz;
use strict;
use warnings;
use Baz;
sub baz { }
1;

$ perl Baz.pm
Subroutine baz redefined at Baz.pm line 5.

If you are going to use the same file both via use or require and as a main script or via do, you should manually put a "BEGIN { $INC{Module.pm} ||= __FILE__ }" in Module.pm before any possible use/require.

[prowler]

So the use/require check is based on whether the module has been loaded by use/require before, and doesn't count the explicit loading of the module at the command line? Thanks for the info - that explains why no warnings were output when the script was actually in use then.

As I hinted at in the original message (but didn't make very clear) the reason that I noticed (and was annoyed by) those warnings was that Eclipse (with the Perl plugin) does compile time checking of code and provides a list of the errors/warnings it can find - this was being cluttered up by those warnings.