On Thu, 20 Jun 2002, Doug MacEachern wrote: > > Apache::PostConfig::Whatever > > instead of: > > Apache::PostConfigWhatever > > that's up to you for your examples. but i personally won't be changing to > that convention. true facts that another level of namespace eat more > memory and take longer to lookup, personally, i find it ugly. > also, the more structures in memory the longer it will take for > perl_clone() to run. both modperl use that as does threads.pm. > so the argument of "memory is cheap" doesn't fly as well with threads. > > perhaps asking [EMAIL PROTECTED] why the module list says: > "Please avoid using more than one level of nesting for module names > (packages or classes within modules can, of course, use any number)." > > would shed more light.
I thought it was just because Tim (I think it was; cc'ed) likes it better that way. =) Maybe there's a more technical explanation. Tim? - ask -- ask bjoern hansen, http://askbjoernhansen.com/ !try; do(); --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
