Re: Understanding the inner workings: getting to know how functions are called
Re: Understanding the inner workings: getting to know how functions are called
- Subject: Re: Understanding the inner workings: getting to know how functions are called
- From: "Kyle Sluder" <email@hidden>
- Date: Tue, 22 Jan 2008 11:26:48 -0500
On 1/22/08, Mattias Arrelid <email@hidden> wrote:
> Could anyone point me in the right direction here? I'm open to all
> suggestions...
I'd create a subclass of NSProxy, override
-methodSignatureForSelector: and -forwardInvocation: appropriately
(perhaps putting a breakpoint in -forwardInvocation: that prints a
backtrace and auto-continues), and return an instance of this from
your real object's -init method. If you do it right, clients of your
class should be none the wiser.
HTH,
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden