On Fri, Apr 11, 2008 at 12:26 AM, Jerry Krinock <[EMAIL PROTECTED]> wrote: > That's fine if the classes exist in all the OS versions, but more commonly > you'll want to use complete classes that are not available in earlier SDK, > of which there are many, especially in Leopard. Code instantiating such > classes must be put in separate bundles that are loaded when the user > activates a Tiger/Leopard-only feature that requires instantiating a > Tiger/Leopard-only class.
This is only true if you are subclassing these classes. If you're only messaging/instantiating them, then you can use NSClassFromString instead of the raw class name to safely reference them without blowing up on the OSes that don't have them. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
