Xref: utzoo comp.sys.next:8668 comp.lang.objective-c:42
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!uunet!hsi!stpstn!lerman
From: lerman@stpstn.UUCP (Ken Lerman)
Newsgroups: comp.sys.next,comp.lang.objective-c
Subject: Re: probate
Message-ID: <5688@stpstn.UUCP>
Date: 16 Oct 90 11:17:38 GMT
References: <3861@network.ucsd.edu>
Reply-To: lerman@stpstn.UUCP (Ken Lerman)
Organization: The Stepstone Corporation, Sandy Hook, CT 06482
Lines: 33

In article <3861@network.ucsd.edu> pbiron@weber.ucsd.edu (Paul Biron) writes:
->
->I'm trying to figure out an "elegent" way to keep a sub-class
->from inheriting methods from its super-class.  In this case,
->I'm making a Stack class out of the List class.  Since a
->Stack should specifically deny "random" access to its elements,
->I need a way to keep it from inheriting ObjectAt:, etc.
->
->So far, all I've done is defined these kinds of methods like:
->
->- ObjectAt:(int)num
->{
->	fputs ("Stack does not recognize selector ObjectAt:\n", stderr) ;
->	kill (getpid (), SIGIO) ;
->}
->
[...]
->Paul Biron      pbiron@ucsd.edu        (619) 534-5758
->Central University Library, Mail Code C-075-R
->Social Sciences DataBase Project
->University of California, San Diego, La Jolla, Ca. 92093

At Stepstone, we write:
    return [self shouldNotImplement:_cmd from:Object];

or:
    return [self notImplemented:_cmd];

depending on the situation.

In this matter, I write only for myself; not for Stepstone.

Ken