• 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: Daniel Jalkut <email@hidden>
  • Date: Tue, 14 Feb 2006 13:51:58 -0500

On Feb 14, 2006, at 1:46 PM, M. Carlson wrote:
On Tue, 14 Feb 2006 18:40:13 Martin Hairer wrote:
"on PowerPC based machines the return value is undefined"

... which begs the question: Why doesn't it / can't it simply return 0 like it should?

On Mac OS X today (10.4.4 PowerPC), the same Objective-C messaging function(objc_msgSend) is used for both float-returning and scalar- returning method signatures.


So to get the desired behavior, I guess objc_msgSend's nil-case handler would have to always obliterate $f1, which might be needlessly costly (and could violate an ABI spec, not sure).

If you're curous about this stuff, you can always disassemble your code and examine the objective-C messaging functions being used. The source code to all of this is available in the objc darwin project.

Daniel

_______________________________________________
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


References: 
 >Re: floatValue of nil NSNumber unreliable (was Re: Bug or feature?) (From: "M. Carlson" <email@hidden>)

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