Re: Why Don't Cocoa's (Un)Archiving Methods return Errors?
Re: Why Don't Cocoa's (Un)Archiving Methods return Errors?
- Subject: Re: Why Don't Cocoa's (Un)Archiving Methods return Errors?
- From: Graham Cox <email@hidden>
- Date: Tue, 02 Aug 2011 10:52:39 +1000
Only vaguely following this thread, but two observations occur (rather obvious ones at that):
a) NSKeyed(Un)Archiver can take a delegate
b) NSKeyed(Un)Archiver can be subclassed
The first allows you to refine the behaviour of the standard object, the second allows you to reimplement it any way you please, while keeping the same overall approach.
So, if you feel the built-in class lacks for something, you can easily take the matter into your own hands.
--Graham
On 02/08/2011, at 9:29 AM, Jerry Krinock wrote:
>
> On 2011 Aug 01, at 12:45, Martin Wierschin wrote:
>
>> This is even worse than the original problem. Rather than getting an exception at the time of encoding, now you're silently converting unencodable objects to strings.
>
> Thank you, Martin. That is correct.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden