Is a cyclic dependency solved with require? - perl

Question

I noticed that I had a cyclic dependency in 2 of my modules. So I did the following:
package A::B::ModuleA;
sub foo {
my ($class, $params) = #_;
# some processing
require A::C::ModuleB;
my $mb = A::C::ModuleB->new();
$mb->bar($params);
# some other processing
}
1;
package A::C::ModuleB;
sub process {
my ($class, $input) = #_;
# Some processing
require A::B::ModuleA;
my $ma = A::B::ModuleA;
$ma->submit($input);
# some other processing
}
1;
So my question is, if the way that I have addressed the cyclic dependency problem via the require inside the function solves any kind of issue that could be a result of such a dependency.

Answer 1

For purely object-oriented code, there is no circular dependency problem. You can quite happily have something like:
# AAAA.pm
package AAAA;
use strict;
use warnings;
use BBBB;
sub new {
my $class = shift;
my ($i) = #_;
bless {
b => $i > 0 ? BBBB->new($i-1) : $i
}, $class;
}
1;
# BBBB.pm
package BBBB;
use strict;
use warnings;
use AAAA;
sub new {
my $class = shift;
my ($i) = #_;
bless {
a => $i > 0 ? AAAA->new($i-1) : $i
}, $class;
}
1;
# script.pl
use strict;
use warnings;
use AAAA;
use Data::Dumper;
print Dumper( AAAA->new(4) );
Circular dependencies only become an issue if you need do something with a module at compile-time. Exporters are the most common example of this.