On 22 Sep 2013, at 10:07, Graham Cox <graham....@bigpond.com> wrote:
> > On 21/09/2013, at 5:13 PM, Dave <d...@looktowindward.com> wrote: > >> Also CF objects will throw an exception if you call release with a nil >> pointer, so you can check for this in your setter. > > > Not if there is a specific retain/release function such as CGImageRetain, > CGImageRelease. These ignore nil. You should always use these instead of a > generic CFRelease because they may do additional work for all we know. That's true, although its probably better to check in either case rather than make an unnecessary CF call. According to the documentation CFRelease or the specialised version can be called, If you have already checked for nil, then there is no reason to have CF do it again I suppose so use CFRelease. All the Best Dave _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
