Re: Category conflicts with Tiger
Re: Category conflicts with Tiger
- Subject: Re: Category conflicts with Tiger
- From: Scott Anguish <email@hidden>
- Date: Sun, 8 May 2005 06:14:49 -0400
This is sage advice. Also, be sure to name your classes with a prefix to similarly protect yourself. On May 8, 2005, at 4:43 AM, Daniel Jalkut wrote: It sounds like the moral of the story is to always name your category methods on system classes with purposely obtuse names. Even if Apple adds a "copy:" method to some class in the future, it seems like it would be risky to assume that it behave the same and has the same side effects as the one we implement today.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden