Re: Implementing Leopard features with Tiger compatibility
Re: Implementing Leopard features with Tiger compatibility
- Subject: Re: Implementing Leopard features with Tiger compatibility
- From: "Kyle Sluder" <email@hidden>
- Date: Fri, 18 Jan 2008 01:35:41 -0500
On Jan 18, 2008 1:13 AM, Doug Knowles <email@hidden> wrote:
> I assume that I should link against the Leopard framework(s) to get at the
> Leopard features, and that I need to test, at runtime, for the availability
> of the Leopard-specific methods with respondsToSelector:. Is that the right
> approach? (I'm on the road right now without access to a Tiger machine,
> otherwise I'd build a test case.)
>
> Of course, if not properly shielded by tests, calls to Leopard APIs will
> trigger runtime failures on Tiger. I'd like to catch these in the build
> phase rather than counting on the QA testing to find them.
What you're describing is called weak-linking. Read
http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/WeakLinking.html
for more information.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden