From: Patrick G. <cap...@sl...> - 2001-04-20 14:12:33
|
The other day, in IRC, was were talking about how Utility.pm has become an orphanage of methods, and how it might be time to look at grouping different methods in Utility into their own modules. One nice way of doing this would be to have the new modules be submodules of Utility, and be able to use Utility the same way we do now without having to worry about what particular sub module to use (the way CGI.pm does it). In looking at CGI.pm briefly, I notice it uses autoloader and other means of doing this (I'm no expert on how CGI.pm is coded) How might we go about implementing this for Utility? What does it mean for memory usage (preventing Utility to be to huge) ? Thoughts? |