Re: [self init] vs. [super init] in initWithCoder
Re: [self init] vs. [super init] in initWithCoder
- Subject: Re: [self init] vs. [super init] in initWithCoder
- From: Byron Wright <email@hidden>
- Date: Thu, 17 Aug 2006 22:45:51 -0700
If you have a base class that implements NSCoding you'd call [self
init], if you have subclasses of this base class then you'd call
[super initWithCoder:] so the whole class hierarchy can be unarchived/
archived.
On Aug 17, 2006, at 8:26 PM, John McLaughlin wrote:
I was pounding my head against a bug last night that ended up being
caused by the fact that I had used [super init] within
initWithCoder instead of [self init] (I set up some notifications
in [self init] that, well, weren't being set up)
It got me to thinking, it seems the convention is to call [super
init] within initWithCoder, most code examples do this. Is there a
reason you wouldn't as a rule call [self init]?
The only reason I can think of offhand is a little performance hit
(since possibly you are creating object in [self init] that you
promptly overwrite in initWIthCoder) but except for that I really
can't think of a good reason not to call [self init] (which, of
course, will call [super init]) and it seems to me to be a best
practice.
Am I missing something obvious here?
-John
John McLaughlin
http://www.loghound.com
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40bluebearstudio.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden