From: "Dirk Bremer" <[EMAIL PROTECTED]> > 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.
So go ahead and improve the module ... :-) And besides ... if it's written in C you are quite unlikely to be able to write anything quicker in pure Perl. > There > is also additional overhead involved for modules that export items. I don't think this makes any measurable difference. Unless maybe if the module exports hundreds of symbols. > There may be occasions where you want a subset of a module's > functionality without incurring the overhead of loading the entire > module. That's what autoload/autosplit was made for. But in most cases the startup cost is either irrelevant (I don't mind if a service starts in 2 secs or 1.7 secs) or can be removed using things like mod_perl or PerlEx. Which will make much bigger difference because it'll remove other more important overheads. In either case ... computing power is cheap, programmer's time is expensive. Jenda =========== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ========== There is a reason for living. There must be. I've seen it somewhere. It's just that in the mess on my table ... and in my brain. I can't find it. --- me _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
