You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2004/07/23 21:46:17 UTC
multi :: packages like Apache::Request::Upload::Brigade::READ is
a bad idea
I've just noticed things like: Apache::Request::Upload::Brigade::READ -
it's not the most efficient choice. The more :: you have in the package
name the longer it'll take for Perl to traverse the linked list of globs
to get to the last entry. Doug who's an "efficiency-freak" advised to
never use more than one ::, or at at most two.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: multi :: packages like Apache::Request::Upload::Brigade::READ is a bad idea
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Stas Bekman <st...@stason.org> writes:
> I've just noticed things like: Apache::Request::Upload::Brigade::READ -
> it's not the most efficient choice. The more :: you have in the package name
> the longer it'll take for Perl to traverse the linked list of globs to get to
> the last entry. Doug who's an "efficiency-freak" advised to never use
> more than one ::, or at at most two.
Thanks for point that out. One obvious thing is that ::Request
does not belong in the name at all- that was a mistake (independent
of the efficiency argument).
--
Joe Schaefer