On 18 Dec 2009, at 21:52, Dave Keck wrote:
>
> Why not use NSKeyedArchiver?
Because it can handle only certain strings?
Because it creates significanly bigger files?
Kind regards,
Gerriet.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
On Dec 18, 2009, at 6:33 AM, Dave Keck wrote:
Why not use NSKeyedArchiver?
It is extremely straight forward to archive certain non-object data
types using NSArchiver and have it interoperate with Core Data and
Cocoa bindings. It is extremely cumbersome to do otherwise. Elegant
versus mes
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
On 19/12/2009, at 12:30 AM, Richard Somers wrote:
> How safe is it to use NSArchiver in a project?
I'd say it's safe, because it will be needed for older file formats that can
only be read by dearchiving using NSUnarchiver. It's not deprecated, it's just
hat newer code is better off using NSK
Why not use NSKeyedArchiver?
___
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 Subscrip
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 legi
