Re: Create App both for Tiger and Leopard
Re: Create App both for Tiger and Leopard
- Subject: Re: Create App both for Tiger and Leopard
- From: Ken Thomases <email@hidden>
- Date: Sun, 18 Jan 2009 06:23:31 -0600
On Jan 18, 2009, at 4:15 AM, Vitaly Ovchinnikov wrote:
Well, after reading your link one more time, I found this:
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/Using/chapter_3_section_4.html#/
/apple_ref/doc/uid/20002000-1114537
So, I am right for Tiger and Leo, that OSX uses lazy loading and if I
never call NSPredicateEditor-related code, I will have no problems on
Tiger?
Basically correct. The term you want to focus on is "weak linking",
rather than "lazy loading".
When you compile with the 10.5 SDK but set a deployment target of
10.4, then any symbols which are new to 10.5 will be linked weakly.
At load time, the dynamic loader (dyld) will not prevent your program
from loading just because weak symbols can't be resolved.
Then it's your code's responsibility to avoid using the missing
functionality. Your strategy of using different nibs is one way to
achieve that. Using -respondsToSelector: for Objective-C methods is
another tool. For functions or variables, you need to test if the
address of the symbol is not NULL before using it.
Regards,
Ken
_______________________________________________
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