Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!argosy!kentb
From: kentb@argosy.UUCP (Kent Beck)
Newsgroups: comp.lang.smalltalk
Subject: Re: Using methods in the superclass' superclass
Message-ID: <1341@argosy.UUCP>
Date: 16 May 91 16:07:21 GMT
References: <28319BCD.B2F@deneva.sdd.trw.com>
Sender: news@argosy.UUCP
Reply-To: kentb@cerebus.UUCP (Kent Beck)
Organization: MasPar Computer Corp, Sunnyvale CA
Lines: 24

For example:

A superclass: Object
A>>initialize
    ...

B superclass: A
B>>initialize
    ...
    super initialize

C superclass: B
C>>initialize
    ...
    A's initialize, but not B's

The program transformation I use in this case is to break A>>initialize
into submethods (i.e. initialize sends "self initializeFoo"), then
C>>initialize can send "self initializeFoo" instead of "super initialize".
In practice I find that this situation arises when I have one method doing
too many things, so the resulting code is cleaner and easier to 
understand.

Kent