I don't believe such a switch exists since it's not really a compiler
issue: using a 10.5+ method is completely legal for your
configuration. A quick way to check what 10.5 methods you're using
would be to set the SDK to 10.4 temporarily and see what errors you
get. You can then make sure you're doing the appropriate runtime checks.
steve
On Jun 27, 2009, at 6:34 PM, Lorenzo Thurman wrote:
I have a program which needs to run under 10.4, but I used a method
that
is only defined for 10.5. No biggie, it was easy enough to replace it
with something that works for 10.4. The problem is that I didn't find
this out until I ran the app under 10.4. My apps deployment target is
set to 10.4, and the base SDK is set for 10.5. My question is:
If I inadvertently use a 10.5 only method, is there a way for me to be
warned at compile time? I know I can use define's to use what's
appropriate for a given target, but what if I overlook the fact that a
method is only for 10.5? is there a compiler switch or something
that I
can enable to tell me this?
_______________________________________________
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
