On Wed, Sep 7, 2011 at 10:44 AM, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote: > On Sep 7, 2011, at 10:06 , Sean McBride wrote: >> It's not a case of "trying to take advantage of 10.7 features", it's a case >> of 10.7's "Resume" feature breaking *binary* compatibility of apps built >> with 10.6 deployment & 10.6 SDK. > > Well, if that's so, consider what you're saying: Lion *broke binary > compatibility with 10.6 applications*. If true, that's not at all what this > thread is about. It's also a *much* more serious problem. (Technically > serious, I mean. The practical effect is a different question.)
Anyone who's dealt with Resume can confirm that this is in fact the case. Resume in Lion broke "binary" compatibility with 10.6 apps. We had to scramble to ship Lion compatibility updates for our apps, and the correct way to do this is to call methods that aren't declared in the 10.6 or earlier SDKs. > Again, the point of this thread is that the above general technique is not > the correct way to opt *in* to a Lion feature. However, if you're trying to > opt *out* in order to work around the claimed Lion bug, then I don't see how > there can be any pragmatic objection to your taking this approach. There's no difference between opting "in" and "out" as far as the consequences go. -setRestorationClass: might depend on 10.7-specific Foundation behavior, since it's a Lion-only API. If Foundation is behaving in 10.6 (or earlier) compatibility mode, then you're screwed. Resume was poorly implemented, and there doesn't exist a good backwards-compatibility solution on the Mac or iOS. Apple's answer is a universal "re-test your apps, and re-write them if necessary." --Kyle Sluder _______________________________________________ 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 arch...@mail-archive.com
