Re^2: Module 'use' chains

Keen, thank you for your response. It was very helpful. I know this is dangerous, and in truth I'd rather not do it. However, I've run into a scenario where I in herited a 4K+ line script. I'm in the process of refactoring it now and have busted it up into about 8 modules. The reason why I thought this would be useful is becuase I can't figure out how to "deeply" compile test this. So "undefined" subroutines are going to drive me to heroin at this point becuase perl -c always reports good. And it seems that if I copy/paste the entire chain of 'uses' into all 8 modules it gets really, really confused and can't find all the subs.

Comment on Re^2: Module 'use' chains

Replies are listed 'Best First'.
Re^3: Module 'use' chains by graq (Curate) on Aug 10, 2006 at 07:49 UTC
Sounds to me like you have done a good job in starting to modularise a script, but that some further redesign is required. Without knowing the exact problem, I can't be sure or specific, but if it were me I would sit down with a pad and paper (or some equivalent) to try to re-think the process flow of the script - and how I can make the modules more modular. -=( Graq )=-	[reply]