hi- On Dec 18, 2009, at 8:30 AM, Richard Somers wrote:
> In the class reference and header file for NSArchiver and NSUnarchiver there > is not a single mention of depreciation for these two classes. The only place > that discusses depreciation is in the Archives and Serializations Programming > Guide for Cocoa. > > It would appear that there are still legitimate needs for the archiver. I > think I have one. (It is extremely straight forward archive certain data > types using NSArchiver and put it into Core Data.) > > How safe is it to use NSArchiver in a project? It is probably as safe to use it now as it was to use it before. That means you will be responsible for version control and other things that might make serialized binary archives incompatible. It may be safe in the future too because if it was not then that would break a lot of binaries that have no chance of being recompiled anytime soon. It would also disable applications from being able to upgrade their documents from the old format to the new format as there would be no way to read the old format and then write the new format. But, really. Why use a fragile and unappreciated API when you can use the more modern but a little less efficient key value encoder and decoder. p.s.- If you use certain plugins then where you used NSArchiver before you can not use NSArchiver now so NSArchiver IS obsolete for some uses. thanks!- -lance _______________________________________________ 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
