On Mon, 19 Dec 2005, Perrin Harkins wrote:
Usually circular references like this are not a problem in Perl. The
only issue I know of is when you try to use imported subs or variables
at compile time.
Generally, this is true. Do beware though of code that may lean on perl's
grammar a bit
On Mon, 2005-12-19 at 15:19 -0500, Philip M. Gollucci wrote:
> > On Mon, 2005-12-19 at 15:11 -0500, Philip M. Gollucci wrote:
> >> I've got some code that gets away with a lot of circular references
> >> because of the "magic load order" in the start
On Mon, 2005-12-19 at 15:11 -0500, Philip M. Gollucci wrote:
I've got some code that gets away with a lot of circular references
because of the "magic load order" in the startup.pl file(s).
Usually circular references like this are not a problem in Perl. The
only issue I know
On Mon, 2005-12-19 at 15:11 -0500, Philip M. Gollucci wrote:
> I've got some code that gets away with a lot of circular references
> because of the "magic load order" in the startup.pl file(s).
Usually circular references like this are not a problem in Perl. The
only issue
I've got some code that gets away with a lot of circular references
because of the "magic load order" in the startup.pl file(s).
Are they are CPAN modules i.e. Module::ScanDeps that might be able to
programatically identify thse ?
Its not always A uses B and B uses A it might
