Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is no reason not to use exceptions normally in objective C even to signify business rule exceptions. Apple can say use NSError who cares. Obj C has been around a long time and at one time ALL C++ documentation said the same thing. The reason it doesnt matter how expensive throwing and catching an exception is, is the lifetime of an exception is exceedingly short and...its an EXCEPTION to the normal flow. I have never heard anyone say ever in my life, man that exception took a long time to be thrown and caught. </p> <p>Also, there are people that think that objective C itself is too expensive and code in C or C++ instead. So saying always use NSError is ill-informed and paranoid.</p> <p>But the question of this thread hasnt yet been answered whats the BEST way to throw an exception. The ways to return NSError are obvious.</p> <p>So is it: [NSException raise:... @throw [[NSException alloc] initWithName.... or @throw [[MyCustomException... ?</p> <p>I use the checked/unchecked rule here slightly differently than above.</p> <p>The real difference between the (using the java metaphor here) checked/unchecked is important --> whether you can recover from the exception. And by recover I mean not just NOT crash. </p> <p>So I use custom exception classes with @throw for recoverable exceptions, because its likely I will have some app method looking for certain types of failures in multiple @catch blocks. For example if my app is an ATM machine, I would have a @catch block for the "WithdrawalRequestExceedsBalanceException".</p> <p>I use NSException:raise for runtime exceptions since I have no way to recover from the exception, except to catch it at a higher level and log it. And theres no point in creating a custom class for that.</p> <p>Anyway thats what I do, but if there's a better, similarly expressive way I would like to know as well. In my own code, since I stopped coding C a hella long time ago I never return an NSError even if I am passed one by an API.</p>
    singulars
    1. This table or related slice is empty.
    1. POthrowing an exception in objective-c/cocoa
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdeleted_user
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would recommend attempting to program a server with exceptions as part of the normal flow of error cases before making such generalizing statements as "there is no reason not to use exceptions normally in objective C". Believe it or not, there are reasons to write high performance applications (or at least parts of applications) in ObjC, and throwing exceptions normally seriously hampers performance.
      singulars
      1. PO
      1. USjbenet
    2. COThere are indeed very good reasons why not to use exceptions in Cocoa. See Bill Bumgarner's answer here for more: http://stackoverflow.com/questions/3378696/iphone-try-end-try/3379240#3379240 . He knows what he's talking about (hint: check his employer). Exceptions in Cocoa are treated as unrecoverable errors, and can leave the system in an unstable state. NSError is the way to go for passing general errors around.
      singulars
      1. PO
      1. USBrad Larson
    3. COExceptions are **exceptional**. Business rule failures surely do not qualify. "Finding and designing away exception-heavy code can result in a decent perf win." MSDN via http://www.codinghorror.com/blog/2004/10/creating-more-exceptional-exceptions.html
      singulars
      1. PO
      1. USJonathan Watmough
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload