I have some modules that use each other and am getting subroutine redefined warnings when compilation is done (using perl -c) on one of the modules.

#!/usr/bin/perl

use warnings;
use strict;

use lib '/tmp/';

package Foo;

use Bar;

sub new
{
  my $invocant = shift;
  my $class = ref($invocant) || $invocant;

  my $self = {};
  return $self;
}

sub get_bar
{
  return Bar->new();
}

1;
[download]

#!/usr/bin/perl

use warnings;
use strict;

use lib '/tmp/';

package Bar;

use Foo;

sub new
{
  my $invocant = shift;
  my $class = ref($invocant) || $invocant;

  my $self = {};
  return $self;
}

sub get_foo
{
  return Foo->new();
}

1;
[download]

Subroutine new redefined at Foo.pm line 13.
Subroutine get_bar redefined at Foo.pm line 22.
Foo.pm syntax OK
[download]

This is mainly irritating as it adds to the list of errors and warnings that appear in the Problems tab of Eclipse when editing.

I know that I can disable warning check for those problems (which I don't want to do as it may hide a real problem), or I can remove each module's use of the other and just ensure that the scripts that call these modules use both of them, but it seems to me that this sort of design should be valid.

Does anyone have any ideas of how to cross use modules without having subroutine redefinition issues?

Thanks,