I don't think so. beneath it all each object method needs access to the c
request_rec, and $r needs to keep its singleton nature. which doesn't mean you can't subclass it, you just need to use the bless { r => $r}, $class syntax. that's what I meant by "the same way you can normal Perl objects" - subclasses have a non-standard syntax.
I typically call the superclass constructor and then re-bless the result, or else simply inherit the constructor completely. Those approaches would still work, wouldn't they?
I always thought it was pointlessly dangerous to subclass $r in mp1, but
I know people did it with alarming frequency.
I've never seen it be dangerous, though I suspect it could be abused. but
it's also amazingly powerful
I just mean that people sometimes seem to subclass and create an "is a" relationship when a simple "has a" relationship (a pointer from some other object) would work just as well.
- Perrin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
