in reply to Re: sub classing best practice
in thread sub classing best practice
In answer to some of the questions...
Both need to use the same authentication mechanism, supplied through 4 arguments. And because of state issues, the authentication state needs to be shared across all transactions. Parent object is authentication + global attribute maniputation, sub classes are manipulation of specific items - in this instance contacts, identities and messages.
My current solution is indeed:
my $subobj = $obj->subclass;
But to me, that doesn't intuitively say I'm creating a new subclass object.
How many years is it 'til Perl 6 again? ;-)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: sub classing best practice
by jbert (Priest) on Dec 11, 2006 at 16:12 UTC | |
|
Re^3: sub classing best practice
by Joost (Canon) on Dec 11, 2006 at 16:10 UTC | |
|
Re^3: sub classing best practice
by polettix (Vicar) on Dec 11, 2006 at 16:20 UTC |