Re: Is a good practice to alloc an object and defer the initialization to another object?
Re: Is a good practice to alloc an object and defer the initialization to another object?
- Subject: Re: Is a good practice to alloc an object and defer the initialization to another object?
- From: Jens Alfke <email@hidden>
- Date: Wed, 10 Feb 2010 12:07:53 -0800
On Feb 10, 2010, at 5:27 AM, Giannandrea Castaldi wrote:
> I would like to alloc an object and defer the initialization to
> another object, is a good practice? The reason is that I can alloc
> several types of objects but the init method have the same signature.
It's unusual, but I've done it once or twice. It looks like:
id obj;
if (.....)
obj = [Class1 alloc];
else
obj = [Class2 alloc];
obj = [obj initWithFoo:.... bar:....];
It's important that you reassign 'obj' to the value of the init call, since initializers are allowed to return a different object than the receiver, and the class-cluster design pattern takes advantage of this.
—Jens
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden