• 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: !foo vs foo == nil
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: !foo vs foo == nil


  • Subject: Re: !foo vs foo == nil
  • From: Torsten Curdt <email@hidden>
  • Date: Thu, 21 Aug 2008 02:43:14 +0200


On Aug 21, 2008, at 01:50, Ken Thomases wrote:

On Aug 20, 2008, at 6:15 PM, Torsten Curdt wrote:

I guess my questions wasn't phrased correctly. The point was more: is 'nil' really the equivalent of 0 or NULL.

Let's put it this way: freshly allocated objects have their memory zeroed out,

Why should that affect the pointer to an object?

cheers
--
Torsten
_______________________________________________

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


  • Follow-Ups:
    • Re: !foo vs foo == nil
      • From: Uli Kusterer <email@hidden>
    • Re: !foo vs foo == nil
      • From: Ken Thomases <email@hidden>
References: 
 >!foo vs foo == nil (From: Torsten Curdt <email@hidden>)
 >Re: !foo vs foo == nil (From: Filip van der Meeren <email@hidden>)
 >Re: !foo vs foo == nil (From: Torsten Curdt <email@hidden>)
 >Re: !foo vs foo == nil (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: creating instance using Class variable
  • Next by Date: Re: !foo vs foo == nil
  • Previous by thread: Re: !foo vs foo == nil
  • Next by thread: Re: !foo vs foo == nil
  • Index(es):
    • Date
    • Thread