My company has a *very* large web application which has evolved over time and has suffered from having many coders of varying abilities hacking away at it. Of the numerous problems it has the first thing I want to tackle is the organization of the many private (ie non CPAN, non standard) modules.
Currently there are lots of situations where a script will use one subroutine from a module which is too broad in scope which pulls in lots of dependencies from all over the tree. This results in a significant proportion (in some cases the majority!) of the exectution time of the script being taken up by importing modules and their dependencies.
I have read and digested the recommendations in perlmodstyle but apart from the obvious things like splitting up the larger modules and making the purpose of each as tightly defined as possible is there any best practice I should be following before I embark on this? Is there anyone else out there who has had to deal with a similar problem and can share their experience with me?Many Thanks
In reply to Private module organisation by Smoothhound
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |