On 20 May 2009, at 16:40, Jerry Krinock wrote:
The new -forwardingTargetForSelector: method in Leopard makes this
sort of forwarding super easy
Until some months later, when you're debugging a "unrecognized
selector sent to class B" message. Ah, three hours later, you
realize that the message was actually sent to class A but was
forwarded to class B.
Surely you'd notice that in the exception's backtrace though?
However, that should only be the case if you unconditionally forward
messages to another object. Sometimes that is the desired behaviour,
in which case the exception is meaningful. In this case, where finite
functionality is being added to the derived classes, they could
conditionally forward only the required methods.
Keith
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
