[Newbies] Design best practice : put state-independent methods on
david.mitchell at gmail.com
Tue Mar 25 19:33:02 UTC 2008
I'm guessing you like that the class methods can be invoked easily
from the class name. What you want is a well known object.
I try to do all my work on the instance side. That's where most of the
I wouldn't use a class object just to create a well known object. I'd
probably start with a Singleton and work from there.
You can see drawbacks and alternatives to Singleton at c2.com:
On Tue, Mar 25, 2008 at 12:41 PM, itsme213 <itsme213 at hotmail.com> wrote:
> I have some methods that currently refer to iVars, called from other methods
> of the same class. I need similar functionality in other classes, not
> related by inheritance, and want to keep it DRY.
> If I move the iVar references into explicit method args they can be easily
> re-located and shared.
> Is it then good or bad practice to take a such collection of related
> state-independent methods (they don't depend on any iVar) and put them on
> the class-side of some suitable class?
> My options and concerns:
> - I could move them up the hierarchy on the instance side but sometimes hit
> single inheritance limits
> - I could use traits for these but am unclear about the future of traits in
> - I can put on the class side and call easily from instance-side methods,
> but is this OK practice?
> Beginners mailing list
> Beginners at lists.squeakfoundation.org
More information about the Beginners