Re: [Moderator] EOT Re: NYT confirms rumor of Apple switch to Intel
Re: [Moderator] EOT Re: NYT confirms rumor of Apple switch to Intel
- Subject: Re: [Moderator] EOT Re: NYT confirms rumor of Apple switch to Intel
- From: Ali Ozer <email@hidden>
- Date: Mon, 6 Jun 2005 22:28:32 -0700
id return types, as well as ints, are OK. So your example is fine. Ali
Begin forwarded message:
From: Jon Hull <email@hidden> Date: June 6, 2005 20:41:57 PDT To: Sean McBride <email@hidden> Cc: Cocoa Developers <email@hidden>, mmalcolm crawford <email@hidden> Subject: Re: [Moderator] EOT Re: NYT confirms rumor of Apple switch to Intel
On 2005-06-06 12:54, mmalcolm crawford said:
Beyond that, there should be little for developers working at the level of abstraction of the Cocoa APIs to be concerned about...
Also: "On a Macintosh using an Intel microprocessor, Objective-C messages sent to nil return garbage for return values that are typed as float or double. On a Macintosh using a PowerPC microprocessor these messages return 0.0."
Of course, no one is relying on the PPC behaviour, right? :)
Does this affect the id return type? Right now, I can (I believe) send messages to nil with no fear of crashing. Can I still do this with nested method calls? For example:
myObj=nil; [[myObj someSubObj]doStuff];
Is this still safe?
|
_______________________________________________
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