Re: call selector @"mySelector"
site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com On Sep 30, 2005, at 7:46 PM, Tom Harrington wrote: On 9/30/05, Raffael Cavallaro <raffaelcavallaro@mac.com> wrote: On Sep 30, 2005, at 3:27 PM, Sherm Pendley wrote: there's NSInvocation. It's more complex, but it's capable of handling any number and type of arguments, and any type of return value. "NSInvocation does not support invocations of methods with either variable numbers of arguments or union arguments." from <http://developer.apple.com/documentation/Cocoa/Reference/ Foundation/ObjC_classic/Classes/NSInvocation.html> sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org _______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.apple... Yes, but "any number...of arguments" != "variable numbers of arguments". Quite right, but I shouldn't have said "any". "any ... type" != "does not support ... union arguments". Although it's a basically a moot point anyway - I can't recall any instance where I've seen a union passed directly by value, i.e. foo (union_var). It's generally passed either by resolving it to one of its specific types, i.e. foo(union_var.int_val), or by passing a pointer, i.e. foo(&union_var). This email sent to site_archiver@lists.apple.com
participants (1)
-
Sherm Pendley