In my most humble opinion, performance. There is no guarantee that the module you want to use was written with performance in mind, and you may encounter situations where performance is a critical issue. There is also additional overhead involved for modules that export items. There may be occasions where you want a subset of a module's functionality without incurring the overhead of loading the entire module. There are probably other reasons/justifications as well.
Dirk Bremer - Systems Programmer II - ESS/AMS - NISC St. Peters 636-922-9158 ext. 652 fax 636-447-4471 [EMAIL PROTECTED] www.nisc.cc ----- Original Message ----- From: "Peter Verhas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, March 05, 2002 08:16 Subject: avoid Perl modules? > I can not understand why one wants to avoid using a Perl module. If it is > coded in C, maybe I can understand the lack of C compiler availability or > knowledge to compile the module to binary. However when the module is > written in Perl there is no point. If one wants to solve a problem, but > wants to avoid using the module he/she will end up rewriting all the module > functions by him/herself. If this is a homewrok targeting knowledge build: > OK. But other than that I see no point. > > Is there any sound reason not to use modules? > > Peter _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
