Re: Learning the Interface Builder
Re: Learning the Interface Builder
- Subject: Re: Learning the Interface Builder
- From: Jean-Daniel Dupas <email@hidden>
- Date: Fri, 04 Nov 2011 16:23:22 +0100
Le 4 nov. 2011 à 16:14, Matt Neuburg a écrit :
> On Thu, 03 Nov 2011 18:46:13 -0700, Conrad Shultz <email@hidden> said:
>> A great many bugs
>> early on will likely owe to sending messages to nil
>
> It occurs to me (moving slowly but surely off-topic here) that the ARC people missed a trick with this one. One of ARC's most wonderful side-benefits is that it guarantees that any object pointer, strong or weak, that is not pointing to an object, is pointing to nil - because ARC puts it there. This suggests that there could have been a compile switch where what ARC puts there is an object that behaves like nil but also logs "You sent a message to nil" to the console. In fact, ARC could also substitute this object when you assign nil to something in your code. (It already does so much messing with your code that this little addition would be easy.) Then we could really track down those accidental send-to-nil moments.
>
> Is that a wild and crazy idea or what?
"Send to nil" is not consider an error or misbehavior in Cocoa. This is a perfectly valid pattern and is use legitimately at lots of places.
Logging warning in such case would cause far too much noise to be useful.
Moreover, a nil object don't have any type information, so you would not be able to know what should have been the type of the receiver, which make logging such message even more useless.
-- Jean-Daniel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden