• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: A hillegass challenge
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A hillegass challenge


  • Subject: Re: A hillegass challenge
  • From: Michael de Haan <email@hidden>
  • Date: Fri, 4 Dec 2009 06:30:09 -0800

On Dec 4, 2009, at 12:05 AM, Rob Keniger wrote:

>
> 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


Rob and Seth, thank you. Progress!  :-)_______________________________________________

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

References: 
 >A hillegass challenge (From: Michael de Haan <email@hidden>)
 >Re: A hillegass challenge (From: Seth Willits <email@hidden>)
 >Re: A hillegass challenge (From: Rob Keniger <email@hidden>)

  • Prev by Date: NSTextView & Horizontal Scrollbar bug
  • Next by Date: Re: IKImageBrowserView D&D with IKImageBrowserNSDataRepresentationType
  • Previous by thread: Re: A hillegass challenge
  • Next by thread: Re: A hillegass challenge
  • Index(es):
    • Date
    • Thread