Relax. I'm sorry but this is simply not where I want to go. I'm not interested in writing code that does something that the system already does. At the same time, I want to provide that missing functionality on older versions of Mac OS X without having two versions of source code, if at all possible. Consider it an academic exercise. It is not the end of the world and I am not the devil.
I do appreciate everyones responses, though. This is a nice place to learn new things. I reserve the right, however, to set my own policy with regard to what I will create and how I make use of our combined expertise in doing so. Have a great day, fellas. -Michael On Jan 23, 2014, at 2:45 PM, Jens Alfke <[email protected]> wrote: > > On Jan 20, 2014, at 12:27 PM, Michael Crawford <[email protected]> > wrote: > >> As I'm sure you are aware, 10.8 now defines a method that does the same >> thing using the same name. > > That's exactly why you should unambiguously prefix the names of category > methods you add to system classes. Collisions are dangerous. Change your > method name to "mc_CGColor" or whatever, and this won't be an issue. > > —Jens > > PS: And let's not turn this into another thread about the need for > namespacing in Obj-C. If anyone's interested in the topic they can search for > the many, many previous messages on this topic here and in xcode-users and > objc-language. And if anyone really needs to post new stuff about it, please > use objc-language as the forum. > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
