On 15 Dec 2014, at 12:42, Jean-Daniel Dupas <mail...@xenonium.com> wrote: > I found only 5 classes that does not responds to isProxy and they are all > internal classes, so real code will never have to deal with instances of such > classes.
Maxthon is iterating over the classes in the system. Even internal classes to the OS show up in that list, so I really don't see how he would *not* have to be able to at least deal with their presence. Apart from completely re-thinking his approach. E.g. NSImageRep, AFAIK, simply has each image representation subclass add itself to an NSArray from its +initialize method. I'd think that'd be less fragile than walking the entire class list. -- Uli _______________________________________________ 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
