Re: A hillegass challenge
Re: A hillegass challenge
- Subject: Re: A hillegass challenge
- From: Rob Keniger <email@hidden>
- Date: Fri, 4 Dec 2009 18:05:36 +1000
On 04/12/2009, at 5:55 PM, Seth Willits wrote:
>> My question pertains to knowingly setting an object to NULL and then knowingly sending it a message as an acceptable technique.
>
> As general answer: Yep. Happens all the time.
As Seth points out, this is perfectly normal. However, you should generally use "nil" instead of "NULL" for nil objects in Objective-C.
It doesn't matter from a technical point of view (they're both the same) but it's the accepted coding style.
--
Rob Keniger
_______________________________________________
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