Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: subclassing NSArrayController

On Mar 3, 2004, at 11:23 AM, Allan Odgaard wrote:

On 3. Mar 2004, at 19:08, mmalcolm crawford wrote:

[...] neither NSArrayController nor its two superclasses [...] implements init:
This is misleading at best. Every class has a designated initialiser. In the absence of other initialisation methods, it is init. Whether or not NSObjectController or NSController implement init is irrelevant to the issue.
The problem I think is, that initWithCoder is not really part of the "designated initializer" convention.

That's not the "problem", that's simply the situation. initWithCoder: clearly addresses a different situation than "standard" object creation. The idea is not to *initialise* the object per se, it's to restore it to the state in which it was at the time it was archived. The object's designated initialiser will have been called when it was created, but that time is now past, and it should not be reinitialised.

mmalc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >subclassing NSArrayController (From: Stefan Fisk <email@hidden>)
 >Re: subclassing NSArrayController (From: Allan Odgaard <email@hidden>)
 >Re: subclassing NSArrayController (From: Stefan Fisk <email@hidden>)
 >Re: subclassing NSArrayController (From: Allan Odgaard <email@hidden>)
 >Re: subclassing NSArrayController (From: mmalcolm crawford <email@hidden>)
 >Re: subclassing NSArrayController (From: Allan Odgaard <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.