Re: Unavailable Function Errors and Backwards Compatability
Re: Unavailable Function Errors and Backwards Compatability
- Subject: Re: Unavailable Function Errors and Backwards Compatability
- From: David Alger <email@hidden>
- Date: Wed, 14 Mar 2007 20:33:00 -0500
On Mar 14, 2007, at 11:31 AM, Sean McBride wrote: On 3/13/07 9:32 PM, David Alger said:
I have looked all over for this, but can't seem to find a way. I want Xcode to emit an error when I try using functions that are not available in 10.3.9 and earlier while at the same time compiling against the 10.4u SDK. Is there a way to do this.
I have tried setting these defines...
#define MAC_OS_X_VERSION_MIN_REQUIRED MAC_OS_X_VERSION_10_3 #define MAC_OS_X_VERSION_MAX_ALLOWED MAC_OS_X_VERSION_10_3
You are not supposed to #define these in your code.
That isn't true, read AvailabilityMacros.h. That is also where they are given there default values if not previously defined. If I don't define them, I don't get warnings. If I define them as such I get deprecation warnings.
I pre-compiled a source file with a function only available in 10.4 called in it. This is what I get, "void Foo() __attribute__((unavailable));" This, as far as I'm concerned, should throw an error like the header says it should. Unless I'm doing something wrong that is.
David This has been discussed many times in the past, see for example:
Yes I did look at this, BTW. -- ____________________________________________________________ Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada
-- David Alger, Software Engineer Family Friendly Software, LLC
Looking for a reliable, affordable, and customer oriented web host? With BlueHost you get a FREE domain name and FREE setup plus a first-class hosting package for ONLY $6.95 a month!
|
_______________________________________________
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