On May 12, 2009, at 12:58 AM, Michael Ash wrote: [snip]
My suggestion would be, if at all possible, avoid creating the NSInvocation manually at all. By far the nicest way to create an invocation is by capturing it using the -forwardInvocation: method. That way you create it using the same syntax you use to send any other message, and the runtime takes care of all the icky details like argument sizes.
I would love to do that. I'm trying to allow partial mocking of internal objects. The current code creates a partial mock as a proxy, which makes getting the invocation really easy. Unfortunately, it means you can't mock a method that is called inside the object.
To work around this, I'm dynamically creating a subclass which overrides the methods I want to mock. This allows me to mock methods on calls to self. Unfortunately, I no longer get an NSInvocation.
I was looking at removing all of the methods on the parent and handling them all with my own dispatch, but removing methods seems to be deprecated in 2.0. Can anyone think of another way to get an invocation?
If not, I'll just build the table and parse things myself. I'll definitely skip structs.
Mike
Mike
-- Mike Mangino http://www.elevatedrails.com _______________________________________________ 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
