<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body><br><hr id="stopSpelling">> Date: Thu, 5 Jul 2007 15:25:12 -0700<br>> From: andreas.raab@gmx.de<br>> To: squeak-dev@lists.squeakfoundation.org<br>> Subject: Re: Spoon planning<br>> <br>> For example, I consider the collection refactoring using traits a <br>> "non-real" example; nobody really has that problem it's purely <br>> academical and of no practical use.<br><br>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.<br><br /><hr />PC Magazine’s 2007 editors’ choice for best web mail—award-winning Windows Live Hotmail. <a href='http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HMWL_mini_pcmag_0707' target='_new'>Check it out!</a></body>
</html>