"weak link" framework refs for 10.1 compatibility?

FROM : Dan Wood
DATE : Thu Nov 07 20:20:10 2002

I'm trying to add some AddressBook framework and NSAppleScript
functionality to my app, but still allow for 10.1 compatibility.  I'm
making sure that no 10.2-specific methods get called in my code, and
that's straightforward, but what is a problem is the constants (e.g.
the Address Book constants in ABGlobals.h, or
NSAppleScriptErrorMessage) are declared within the frameworks, that
cause the bundle not to load in 10.1.

I've found a workaround is to use my own string constants -- e.g.
@"NSAppleScriptErrorMessage" instead of NSAppleScriptErrorMessage --
but that seems like such a hack.  Is there a better way around this
problem, like some sort of "weak linking" (for lack of a better term)
that will cause the code not to complain that it can't find the string
constants in the 10.1 frameworks, since the code will never be executed?



--
Dan Wood
Karelia Software, LLC
<email_removed>
http://www.karelia.com/
Watson for Mac OS X: http://www.karelia.com/watson/
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.