On 5 May 2010 18:34, Michael Haupt <mhaupt at gmail.com> wrote:
> Hi,
>
> On Wed, May 5, 2010 at 5:12 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> Overrides are evil, period.
>
> question mark.
>
> Imagine some class being loaded that right- and joyfully overrides a
> method whose implementation solely consists of sending
> #subclassResponsibility to self. I do *not* want to confirm that. It's
> *intended*.
>
I think we confusing the terms here.
An MC's override is not 'implementing different version of some method
in subclass, while base class already having this method implemented'.
An MC's override is 'overWrite/replace existing method in 3-rd party
class by own version'.
See the difference?

> Specialisation is an important feature in OOP, right? From time to
> time, it's just needed.
>
> Now imagine someone who is not too experienced in Squeak and who wants
> to load some interesting package for playing around with it. Those
> "Override! Warning! Careful!" messages will quickly repel that person
> (at least: deeply unsettle them), and BOOM! we have one more Ruby
> programmer. ;-)
>
A subclass overrides are fine, since they not replacing a method in a
base class.

> Best,
>
> Michael
>
>



-- 
Best regards,
Igor Stasenko AKA sig.