• 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: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)


  • Subject: Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
  • From: Jim Correia <email@hidden>
  • Date: Tue, 14 Feb 2006 16:18:35 -0500

On Feb 14, 2006, at 1:31 PM, M. Carlson wrote:

From this Apple statement:

"The Objective-C runtime assumes that the return value of a message sent to a nil object is nil, as long as the message returns an object or any integer scalar of size less than or equal to sizeof (void*)."


Would it be fair to conclude that a float value takes up more stack space than an integer

"any *integer* scalar of size less than or equal to..."

A float is not an integer.

Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
      • From: Andrew White <email@hidden>
References: 
 >RE: floatValue of nil NSNumber unreliable (was Re: Bug or feature?) (From: "M. Carlson" <email@hidden>)

  • Prev by Date: Re: setting NSSlider floatvalue from different thread
  • Next by Date: Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
  • Previous by thread: Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
  • Next by thread: Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?)
  • Index(es):
    • Date
    • Thread