In that case, all I can think of is parsing all the project the .m files, finding the method implementation and storing what string is declared within the parens.
Build the table before compilation or at, store it in plists for each class and read the plist for each class to determine the expected return value for each method. Is that massive overkill, or does sound reasonable? Sent from my iPad. Please pardon typos. On Feb 23, 2015, at 1:31 AM, Kyle Sluder <k...@ksluder.com> wrote: > On Mon, Feb 23, 2015, at 12:18 AM, Maxthon Chan wrote: >> In Objective-C, methods are called my sending messages, and message >> selectors are not bounded to a class. >> >> You can walk all loaded classes and try to work out the classes that >> responds to the message selector in question, but beware classes that >> descended from the old Object class (not NSObject or NSProxy) that does >> not work with (most) introspection methods and runtime functions. > > For those who have only read the subject line: this thread isn't about > finding out what class an IMP belongs to. It's about finding out what > class of object a method is declared to return. And that information > simply is not available. > > --Kyle Sluder > _______________________________________________ > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
