• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSError: why returned directly?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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
  • Follow-Ups:
    • Re: NSError: why returned directly?
      • From: William Bumgarner <email@hidden>
References: 
 >Re: NSError: why returned directly? (From: Erik Buck <email@hidden>)
 >Re: NSError: why returned directly? (From: Jonathon Mah <email@hidden>)
 >Re: NSError: why returned directly? (From: William Bumgarner <email@hidden>)

  • Prev by Date: Re: NSError: why returned directly?
  • Next by Date: Re: FYI: Cocoa's framework scaling works great!
  • Previous by thread: Re: catches in @catches (was: NSError: why returned directly?)
  • Next by thread: Re: NSError: why returned directly?
  • Index(es):
    • Date
    • Thread