Re: pragma nowarn
Re: pragma nowarn
- Subject: Re: pragma nowarn
- From: Alastair Houghton <email@hidden>
- Date: Wed, 12 Dec 2007 13:25:01 +0000
On 12 Dec 2007, at 13:20, Alexander v. Below wrote:
So build against the 10.3 SDK (or the 10.4 or 10.5 SDKs) instead,
setting the "Mac OS X Deployment Target" build setting to 10.2.
Then the method will have been declared by the framework headers.
(There are hackier solutions, for instance declaring the method
yourself e.g. on a category of NSNotificationCenter. But the
officially supported one is using the newer SDK and the deployment
target setting.)
Well, but generally I want to know about anything I am using that is
not in 10.2 - or, let's call it SDK(n-1).
You might want to look at my recent post in Cocoa-dev on that topic
(titled "Re: Making sure my code will run on Tiger 10.4 when I'm
compiling on Leopard 10.5"), since that's certainly a problem. I
imagine you probably want to file a bug report to ditto the one I
filed two years ago, if you haven't already.
I think this is a good example where you want fine-graning "no
warnings" areas. performSelector: will not cut it, because there are
too many arguments, so I am probably left with some NSInvocation
voodoo.
Moving it into a category, if I am not mistaken, will just move the
warning to a different place.
Why do you say that? I don't believe you get any warnings in such a
situation. That's why categories are often used for e.g. delegate
methods.
Of course, if you use the category solution and later start building
against a newer SDK, then you may run into problems. But I'm fairly
certain the category solution will get rid of the warnings for you.
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden