> > WRT to CPAN, as a system administrator, you do basically want to maintain > the smallest number of independent bits of software on the machines you > run, but when a CPAN module depends on several others, each of which depends > on several others etc, you can have a potential nightmare on your hands.[1] > > [1] In this case, I'm counting stuff in the core as part of the core, and > not as an independent software package. > > I'm curious to know what people's solutions are to this problem, as it seems > to go against code-reuse. I can only imagine that the right answer is some > sort of compromise. >
Generally, when big chunks of code are coming together .... the name/variable space needs to guarantee uniqueness ... in this way code won't glob over the top of previous code (e.g., Java's packaging system helps to police this due to the assumption about namespaces - in reverse dns order: com.companyname.modulename) Because the namespace resolves to directories and files ... loading and pre-requisite checking can be automated ... in the case of Perl the namespace can't be guaranteed in the same way as Java ... Nige -- Nigel Hamilton Turbo10 Metasearch Engine email: [EMAIL PROTECTED] tel: +44 (0) 207 987 5460 fax: +44 (0) 207 987 5468 ________________________________________________________________________________ http://turbo10.com Search Deeper. Browse Faster.
