Smalltalk › Squeak › Squeak - Dev

RE: Spoon planning

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

J J-6

RE: Spoon planning

> Date: Thu, 5 Jul 2007 15:25:12 -0700
> From: [hidden email]
> To: [hidden email]
> Subject: Re: Spoon planning
>
> For example, I consider the collection refactoring using traits a
> "non-real" example; nobody really has that problem it's purely
> academical and of no practical use.

Hrm, so do you think the way the collection heirachy is correct as it is? I think there is a bit of duplication and methods that are inherited that should not be, no? Or maybe you think the same, but don't see it as a big deal. I personally think that if they can be refactored to get rid of the subclass #shouldNotImplement overrides and remove duplicate code then it is a win that does have practical use for all the reasons that removing these things normally have.

PC Magazine’s 2007 editors’ choice for best web mail—award-winning Windows Live Hotmail. Check it out!

Damien Cassou-3

Re: Spoon planning

2007/7/20, J J <[hidden email]>:

> ________________________________
> > Date: Thu, 5 Jul 2007 15:25:12 -0700
> > From: [hidden email]
> > To: [hidden email]
> > Subject: Re: Spoon planning
> >
> > For example, I consider the collection refactoring using traits a
> > "non-real" example; nobody really has that problem it's purely
> > academical and of no practical use.
>
> Hrm, so do you think the way the collection heirachy is correct as it is? I
> think there is a bit of duplication and methods that are inherited that
> should not be, no? Or maybe you think the same, but don't see it as a big
> deal. I personally think that if they can be refactored to get rid of the
> subclass #shouldNotImplement overrides and remove duplicate code then it is
> a win that does have practical use for all the reasons that removing these
> things normally have.

I agree with you: having good code is always something interesting if
you don't loose performances.

--
Damien Cassou