开发者

Would it be correct/ellegant use only alloc without init?

开发者 https://www.devze.com 2023-01-23 01:34 出处:网络
If we don\'t want to implement init method in our class, and bearing in mind that init in NSObject only开发者_开发技巧 returns an instance of the object without initialization, I don\'t see the point

If we don't want to implement init method in our class, and bearing in mind that init in NSObject only开发者_开发技巧 returns an instance of the object without initialization, I don't see the point of calling init if we already get the instance with alloc. I have tried and it works, but I am not sure it won't cause future problems.

myClass *newObject = [myClass alloc];

instead of:

myClass *newObject = [[myClass alloc] init];

Thanks a lot.


No, just calling alloc would not be correct. alloc zeroes out all instance variables of the object, init then has the chance to set all or some instance variables to their default values. Some classes even use their init methods to create another instance and return that one instead of the one you allocated.

Many classes expect that their init methods get called and would possibly cause crashes if you don't call init. If you are talking about a custom class that inherits directly from NSObject and needs no initialization of instance variables, you might get away with [myClass alloc] but it is definitely not good programming style.


I think that it is not a good idea.
Read Cocoa Design Pattern, especially the "Two stage creation"

You can also read this article http://www.informit.com/articles/article.aspx?p=1398610


I think that it wouldn't matter much if you didn't implement a "- (id)init" because if you did, you would call NSObject's init method which just returns the same value you send to the method. Though it is a good idea to create your own init method to set your instance variable.


in runtime source code perform -(id)init will call _objc_rootInit(self) and will return self. I guess only perform init is OK。

0

精彩评论

暂无评论...
验证码 换一张
取 消