Re: warning: assignment from distinct Objective-C type
Re: warning: assignment from distinct Objective-C type
- Subject: Re: warning: assignment from distinct Objective-C type
- From: mmalc crawford <email@hidden>
- Date: Tue, 11 Mar 2008 22:39:49 -0700
On Mar 11, 2008, at 6:11 PM, Quincey Morris wrote:
Moreover, a problem with using the "factory method approach" is
that they return autoreleased objects.
If you have a particular need to be concerned about performance (as
you might especially in a resource-constrained environment), it is
generally a Good Thing to avoid autorelease and instead use alloc/
release directly.
There's no reason why it can't be named "create..." and return a
retained object, if that's what's needed in any given situation.
Following standard Cocoa conventions (<http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html
>), the name would be "new..." (and this is a pattern used in some
recent code samples).
But the example you gave, and the most common case in the current
frameworks, is to return an autoreleased object, and it's worth
bringing this issue to others' attention.
mmalc
_______________________________________________
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