• 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: Scott Ribe <email@hidden>
  • Date: Thu, 21 Aug 2008 12:56:23 -0600
  • Thread-topic: !foo vs foo == nil

>> Could you tell me which part of the standard states that NULL is 0.


> NULL *can* be 0, it isn't *necessarily* 0


It follows from the rules re conversions that it must be either 0, or 0 cast
to a pointer type. No value other than 0 is guaranteed to cast to the
machine's actual null address (whatever bit pattern that might actually be).

6.3.2.3 which you quoted, does not provide for any value other than 0.

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

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: "Clark Cox" <email@hidden>
References: 
 >Re: !foo vs foo == nil (From: "Clark Cox" <email@hidden>)

  • Prev by Date: Re: Converting NSString to valid HTML string
  • 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