Re: Making an object accessible by both MyDocument AND a custom class
Re: Making an object accessible by both MyDocument AND a custom class
- Subject: Re: Making an object accessible by both MyDocument AND a custom class
- From: Andreas Mayer <email@hidden>
- Date: Wed, 25 Sep 2002 20:18:27 +0200
Am Mittwoch, 25.09.02 um 19:43 Uhr schrieb Joe Lester:
You certainly CAN send messages to nil! I do it all the time.
Sure you can.
It sends the message up the responder chain.
No it does not. At least I dearly hope it does not!
From Apple's "Object-Oriented Programming and the Objective-C
Language", June 2000, chapter 3, page 53:
"A message to nil is also valid, as long as the message returns an
object; if it does, a message sent to nil will return nil. If the
message sent to nil returns anything other than an object, the return
value is undefined."
Have you not heard of a nil target before? Can I get a witness out
there please?
I'm sorry. :}
bye. Andreas.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.