-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #30 from Tightdb/ks-error-handling-from-jesper
Error handling from Jesper (and much more)
- Loading branch information
Showing
34 changed files
with
1,113 additions
and
1,267 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
Category 1: NSError for "expected" problems | ||
=========================================== | ||
Characterized by: File access problem, network access problems.... User should be informed. Problems which cannot be eliminated during development. | ||
|
||
- Writing a group to a file, with file access problems. | ||
|
||
|
||
Category 2: NSException for "unexpected" problems - no recovery | ||
=============================================================== | ||
Characterized by: Fatal errors. Wrong use of API. Application should rightfully crash. These problems should be eliminated during development. Feedback should be fast and direct in the form of an exception. The | ||
application should not attempt to catch the exception. | ||
|
||
- Indexing out of bounds. | ||
- Passing illegal parameter type. | ||
- Writing to read only table (working assumption). | ||
- Core library exceptions. | ||
|
||
|
||
Category 3: NSException for "unexpected" problems - with recovery | ||
================================================================= | ||
Technically possible with ARC safe exceptions flag. Leads to excessive release code (automatically inserted). Should not be needed. | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.