Implementing Leopard features with Tiger compatibility
Implementing Leopard features with Tiger compatibility
- Subject: Implementing Leopard features with Tiger compatibility
- From: "Doug Knowles" <email@hidden>
- Date: Thu, 17 Jan 2008 22:13:38 -0800
Hi, all,
I need to implement an application that exploits at least some Leopard
features (including Core Animation), but is compatible with Tiger (without
the Leopard features, of course), and I'm trying to figure out how to set up
the project.
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.
I'm thinking about setting up a Tiger-only build configuration linked to the
Tiger frameworks, and requiring the Leopard-dependent code to be wrapped in
conditional compilation to disable it in the Tiger builds. The Tiger builds
would not be intended for release, but we'd include them in the nightly
build procedures to catch improperly wrapped Leopard calls via build errors.
Am I on the right track, or is there a better way to do this?
TIA,
Doug K;
_______________________________________________
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