Skip navigation.
 
mlRe: subclassing a private subclass
FROM : John C. Randolph
DATE : Fri Jan 03 17:07:02 2003

On Friday, January 3, 2003, at 04:36 AM, Finlay Dobbie wrote:

>
> On Friday, January 3, 2003, at 12:18  am, John C. Randolph wrote:
>

>> @interface MyColor : NSObject
>>  {
>>  NSColor *realColor;
>>  // whatever ivars you want to keep
>>  }
>>
>> @end

>
> If you don't want/need to keep ivars, and just want to add a few
> convenience methods, categories are the way to go.


Finlay's right.  My answer presumed that you need to keep additional
state that an NSColor normally wouldn't.

-jcr

John C. Randolph    <<email_removed>>  (408) 974-8819
Sr. Cocoa Software Engineer,
Apple Worldwide Developer Relations
http://developer.apple.com/cocoa/index.html


Related mailsAuthorDate
mlsubclassing a private subclass James Gregurich Jan 2, 16:07
mlRe: subclassing a private subclass John C. Randolph Jan 2, 16:19
mlRe: subclassing a private subclass James Gregurich Jan 2, 19:03
mlRe: subclassing a private subclass Finlay Dobbie Jan 3, 04:37
mlwhy are private classes private? James Gregurich Jan 3, 05:56
mlRe: why are private classes private? Finlay Dobbie Jan 3, 06:21
mlRe: why are private classes private? Clark S. Cox III Jan 3, 06:21
mlRe: why are private classes private? Mike Ferris Jan 3, 09:44
mlRe: subclassing a private subclass John C. Randolph Jan 3, 17:04
mlRe: subclassing a private subclass John C. Randolph Jan 3, 17:07
mlRe: why are private classes private? James Gregurich Jan 3, 19:02
mlRe: why are private classes private? Finlay Dobbie Jan 4, 04:21
mlRe: why are private classes private? Eric Peyton Jan 4, 05:53
mlRe: why are private classes private? Gregory Seidman Jan 4, 07:55
mlRe: why are private classes private? Kenneth C. Dyke Jan 4, 12:26
mlRe: why are private classes private? Mike Ferris Jan 6, 08:12