On Sun, Oct 2, 2011 at 10:51 PM, Rodney Polkinghorne
<rpolkinghorne at groupwise.swin.edu.au> wrote:

>> You should not instantiate an abstract class.
>
> To follow that advice, I'd need a way to find out which classes were
> abstract, and when I'd implemented enough methods to stop them being
> abstract.  That seems to be a black art in Smalltalk.

Yes, the way this is supposed to work is that you look for
subclassResponsibility: methods and override them.   That is why #size
in Collection is wrong; it hides what you are supposed to do.

So, one more vote for fixing this.

-Ralph