>> memory used by the various .pm files that will be loaded numerous
>> times. I can see that grouping functions based on functionality would
>> reduce the number of .pm files in memory. However, if I go that route,
use only loads the .pm once. Multiple uses don't eat up any more resource
than having it done once.
The minimal-module approach can be managed nicely via Autosplit, which
puts eash sub in its own module with a stub AUTOLOAD that snags things
into core only when they are called (the ultimate in lazyness, no?). This is
particularly nice for rarely called modules . One example is speicial exceptions
in database app's. You can put the exception handler into a sub, have autosplit
stuff it into a module and only load it into memory if the error does show up.
This helps with code release issues because the related code lives in a single
moule for editing and testing purposes but only sucks up core when needed.
sl
