• 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: Error and Exception Handling: When to use
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error and Exception Handling: When to use


  • Subject: Re: Error and Exception Handling: When to use
  • From: Uli Kusterer <email@hidden>
  • Date: Wed, 13 Jun 2007 08:13:59 -0700

On Jun 12, 2007, at 10:05 AM, Nelson Santos wrote:
So, if I understand correctly, I should use these two classes to catch as many problems as I can before shipping a finished product. Any exceptions that I throw and forget to catch during my testing phase will ultimately be caught by NSApp and reported to the user, and cause a shutdown of the application. Is that right?

No, it'll not cause a shutdown. I general, it will just cancel the current iteration of the event loop and return to processing events.


Cheers,
-- M. Uli Kusterer
http://www.zathras.de



_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


References: 
 >RE: error handling (From: "Nelson Santos" <email@hidden>)
 >Re: error handling (From: Klaus Backert <email@hidden>)
 >RE: Error and Exception Handling: When to use (From: Nelson Santos <email@hidden>)

  • Prev by Date: Re: Crash with no code of mine. How to debug? (_NSModelObservingTracker)
  • Next by Date: Re: Ending NSTableView editing via textDidEndEditing
  • Previous by thread: RE: Error and Exception Handling: When to use
  • Next by thread: Disabling a particular NSButtonCell in NSTableView
  • Index(es):
    • Date
    • Thread