Comments on: Grab that Invocation

By: chrome

chrome — Sun, 04 Jan 2009 06:43:27 +0000

Great work; saved me a bunch of time writing this myself.

By: chrome

chrome — Sun, 04 Jan 2009 01:43:27 +0000

Great work; saved me a bunch of time writing this myself.

By: Richard Stacpoole

Richard Stacpoole — Thu, 07 Sep 2006 10:49:54 +0000

Thanks,

I have just started using NSInvocation, and this will be useful.

Also there is a bug in your first code box, you have &firstArgument twice.

By: Richard Stacpoole

Richard Stacpoole — Thu, 07 Sep 2006 09:49:54 +0000

Thanks,

I have just started using NSInvocation, and this will be useful.

Also there is a bug in your first code box, you have &firstArgument twice.

By: Lexical » Archive » NSInvocation in Practice

Lexical » Archive » NSInvocation in Practice — Tue, 27 Jun 2006 05:51:11 +0000

[...] There’ve been a few mentions of NSInvocation recently. I have to agree about how useful it can be, and wanted to mention a few specific places I used it in Lexicon. [...]

By: Daniel Jalkut

Daniel Jalkut — Sun, 25 Jun 2006 15:19:49 +0000

Nice work! One possible enhancement might be to change the invocation "capture" so that it can record multiples on an array. Then the client could ask for an array of all invocations sent to it. It could even sport a "performInvocationsOnObject:" method.

Also, the name "CInvocationRecorder" might better represent what this thing does, especially if multi-recording was added.

By: Daniel Jalkut

Daniel Jalkut — Sun, 25 Jun 2006 14:19:49 +0000

Also, the name "CInvocationRecorder" might better represent what this thing does, especially if multi-recording was added.