• 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:19:09 +0200

Erik,

On 26.4.2006, at 16:07, Erik Buck wrote:

We have all been reminded that “goto” is seldom a good idea. Well, an exception is a “goto” with a destination that can not be predicted by the author of the code that generates the exception (“goto”). Exceptions are the most pathological example of goto that is possible.

Exceptions are -- conceptually -- much rather (non-local) breaks than (non-local) gotos. Do you advocate against break, too?
---
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: Erik Buck <email@hidden>
References: 
 >Re: NSError: why returned directly? (From: Erik Buck <email@hidden>)

  • Prev by Date: Re: Flipping over coordinate conversion
  • Next by Date: Re: NSError: why returned directly?
  • Previous by thread: Re: NSError: why returned directly?
  • Next by thread: Re: NSError: why returned directly?
  • Index(es):
    • Date
    • Thread