2007/7/20, J J <azreal1977 at hotmail.com>:
> ________________________________
> > Date: Thu, 5 Jul 2007 15:25:12 -0700
> > From: andreas.raab at gmx.de
> > To: squeak-dev at lists.squeakfoundation.org
> > 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