On Tue, Jun 3, 2008 at 12:01 PM, Charles Srstka <[EMAIL PROTECTED]> wrote: > That's what I was afraid of. So it seems that by using CoreData, one loses > all control over his or her app's file format, which is a shame.
There are plenty of circumstances in which you don't have control over the document format even without Core Data. The Cocoa serialization format is opaque. > It also > means that even for a Mac-only app you could end up with this really weird > situation where an app running on a later version of OS X could end up > saving a file that was unreadable by the same version of the same app that > just happens to be running on an earlier OS X version. This is extremely unlikely to occur in practice. Apple is sensible enough to, in these sorts of circumstances, make these changes depending on which SDK you're compiling against or, since Core Data has versioning support now, silently upgrade files upon opening them. Part of using a framework is knowing that in some circumstances the framework will implement something in a particular manner. Often times in Cocoa, avoiding this implementation means sacrificing a hell of a lot more. --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 [EMAIL PROTECTED]
