Re: Sending messages to nil on Intel
Re: Sending messages to nil on Intel
- Subject: Re: Sending messages to nil on Intel
- From: Felix Schwarz <email@hidden>
- Date: Tue, 2 Aug 2005 00:40:17 +0200
after reading this ..
http://developer.apple.com/documentation/MacOSX/Conceptual/
universal_binary/universal_binary_tips/chapter_5_section_16.html#//
apple_ref/doc/uid/TP40002217-CH239-291803
That is simply reinforcing what the objective-c language guide has
said all along:
"A message to nil also is valid, as long as the message returns an
object; if it does, a message sent to
nil returns nil. If the message sent to nil returns anything other
than an object, the return value is
undefined. "
and further pointing out that because of implementation details of
the runtime on the PowerPC, you may have gotten away with it but on
Intel-based machines, you will not.
Thanks for the info!
So, just so I got things right: as long as I expect back an object as
return value, I may still stack calls. However I should not stack
calls, if I expect anything else like an integer value or a pointer?
Best regards,
Felix
_______________________________________________
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