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: Kyle Sluder <email@hidden>
- Date: Mon, 01 Aug 2011 16:50:43 -0700
On Mon, Aug 1, 2011 at 4:29 PM, Jerry Krinock <email@hidden> wrote:
> Thus, My New Code gives the same result as the Classic Approach, but it does so without raising an exception. So I'm thinking about changing from Classic Approach to My New Code in my next project. I always like to think long and hard before applying a category to NSObject, though.
That is worse. Throwing an exception at a predetermined point is far
superior to maybe throwing an exception sometime in the future when
you happen to send a message that the receiver doesn't respond to.
--Kyle Sluder
_______________________________________________
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