Re: Apache2
Dave Rolsky <[email protected]>
| Newsgroups | gmane.comp.web.mason.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 27 Jul 2004, Jonathan Swartz wrote:
> A subclass does make intuitive sense, but we shouldn't design it that
> way unless we can solve the subclassing-hell problem that occurs when
> users want to subclass our parent classes. (Example: consider how hard
> it is for a user to use their own subclass of Component.pm right now,
> given that Subcomponent.pm inherits from Component.pm).
True. I think it can be done in one class by setting various object/class
attributes to be the right meth/class/whatever based on whether or not
we're using mod_perl 1 or 2. Then we have simpler subroutines without
lots of:
if ( $mod_perl::VERSION >= 1.99 ) {
...
} else {
...
}
The reason I dislike that is the two blocks of the branch generally are
doing the same thing, but they invoke slightly different methods or
classes to do what they want.
-dave
/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click