On Nov 18, 2009, at 11:15 AM, Jim Correia wrote: > This problem is just not restricted to private methods, or additions through > categories. You can also run afoul of a namespace conflict with a public > method in your subclass.
Yes; but this is less likely because Apple engineers add public methods less often (almost never in minor updates) and more carefully. (It would be nice if Obj-C had some sort of namespaces for methods, and it's been discussed, but it sort of conflicts with the dynamic nature of the language. Every message has to have a single canonical name at runtime; if you think about the implications for selector names in source code and in IB, you can see how it would get messy.) —Jens_______________________________________________ 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
