initWith: - Chap 10, pg 206, Prog 10.1

[applefan90]

Instead of overriding self with

Code: (Objective-C)

self = [super init];

Why can't you just do this:

Code: (Objective-C)

[self [super init]];

Hmm, now that I typed it I think I may understand.  Correct me if I'm wrong please:
The method will have to return itself in order to initialize properly.  If you do the previous block of code, you would have no way of returning the overridden self variable.

[skronwith]

My question in all of this is why bother?  That is why bother with writing our own initialization methods?  It may save a few lines of code, though I don't even see it really doing that.  Is there a reason to do this besides a bit of elegance to the code-writing?

[Trimakas]

I'm kinda with you one this one.. I did have a problem understanding this as well.. But someone else's pain helped me to understand what was going on..

Thanks for that!
Todd

[seerex]

The above code you've written doesnt work coz when you say [self [super init]; you arent returning a value to self. You are really trying to call the super init within self. So to speak. Atleast i think so :=) you are accessing the super init within self.

When you do self = [super init]; you call the parents initializer, and the initialized object is returned into self. If you dont do the = assignment operator, it would have no way of returning it.

 As to your question on why you would ever write your own initializer, i was wondering this as well. But trust me, when you start writing some code on your own you will at some point say "hey, if i write a new initializer, i can do this much faster". I did that in my previous project, where i had some values inside a class i knew i needed to set for each instance i created, thus it made sense to make it part of the initialization message.

Hope i helped.

Best Regards
/JBJ