From: Ned Konz <ned@...>
Date: 2002-06-05T07:56:34+09:00
Subject: Re: Calling a (any) superclass method when already have one by that name

On Tuesday 04 June 2002 03:40 pm, Philip Mateescu wrote:
> Wrong ? Nothing, I just wanted another way...
> it somehow seem to me it dimishes the dynamicality of code. I mean
> you have to alias all the methods you wanna use from the superclass
> (and which are overridden in the current class)...

But how often does that happen? In my experience with Smalltalk, not 
too often (though it's easy to call a superclass method in 
Smalltalk).

Given a properly factored design, it's pretty uncommon to need to call 
*different* superclass methods directly (the common case of calling 
the *same* superclass method is already handled with super()).

I would argue that if you find yourself having to do this, you 
probably need to refactor the code and extract the bit that is needed 
by both the superclass and subclass into a separate superclass 
method.

If your subclass doesn't change the meaning of a method, then you 
should be calling your overridden method. Which is easy.

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE