Re: NSError: why returned directly?
Re: NSError: why returned directly?
- Subject: Re: NSError: why returned directly?
- From: Ondra Cada <email@hidden>
- Date: Wed, 26 Apr 2006 20:01:47 +0200
Just for a bit of clarification,
On 26.4.2006, at 17:58, William Bumgarner wrote:
I would very strongly discourage you from using NSExceptions to
indicate anything but programmer error or other internal
assertions. Like it or not, NSError based indication and handling
of runtime errors is the design pattern used throughout AppKit and
Foundation
That's self-evident and I've never ever advocated for something like
reporting runtime errors through NSExceptions.
OTOH, I see (perhaps mistakenly) a lot of advantages in potential
using @throw for reporting NSErrors (along with, but separately from,
NSExceptions -- just like currently they are returned along with, but
separated from, return values).
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden