Re: Category conflicts with Tiger
Re: Category conflicts with Tiger
- Subject: Re: Category conflicts with Tiger
- From: Nicko van Someren <email@hidden>
- Date: Sun, 8 May 2005 11:41:30 +0100
On 8 May 2005, at 11:14, Scott Anguish wrote:
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.
This is sage advice. Also, be sure to name your classes with a prefix
to similarly protect yourself.
Of course this strategy does nothing to help in the case where what you
are trying to do is catch selectors such as copy: cut: and paste: as
they pass up the responder stack, which was a major part of the
original question.
I suggest that to deal with that particular problem you do as was
suggested previously; split out all the parts of the categories that
are needed in 10.3 but not in 10.4 into a separate bundle and put that
bundle inside you application. When your application starts up check
the OS version; if you're running on 10.3 use NSBundle to locate the
code and then call -principalClass on that bundle to force the code
part of the bundle into the running application.
Nicko
_______________________________________________
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