Re: Checking for nil-return
Re: Checking for nil-return
- Subject: Re: Checking for nil-return
- From: Dave Keck <email@hidden>
- Date: Tue, 5 Oct 2010 12:10:35 -0400
> Because it throws exceptions if anything bad happens at runtime (i.e out of memory, invalid parameters etc)
If memory truly becomes exhausted (as opposed to attempting to
allocate a huge object), you'll crash due to a stack overflow since
the code path of throwing an exception allocates objects.
_______________________________________________
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