FROM : Bill Bumgarner
DATE : Sun Jun 25 20:49:14 2006
On Jun 24, 2006, at 7:08 PM, David Dunham wrote:
> On 24 Jun 2006, at 10:58, Bill Bumgarner wrote:
>> If your application encounters an NSException, then the state of
>> the AppKit, Foundation, and CoreData are undefined. NSExceptions
>> are thrown for non-recoverable runtime errors.
>
> So far I've had fairly good luck catching NSException so I can
> report errors when a document can't be read (e.g. the mythic
> NSInvalidArchiveOperationException). Seems like a recoverable error
> to me...
>
> But I'm not using C++ in this app, and I'm catching fairly close to
> the throw.
Sent from xcode-users to Cocoa-dev.
David is correct... it is recoverable in that the app isn't dead.
However, the NSDocument that failed to read is now in an
unrecoverable state....
b.bum
DATE : Sun Jun 25 20:49:14 2006
On Jun 24, 2006, at 7:08 PM, David Dunham wrote:
> On 24 Jun 2006, at 10:58, Bill Bumgarner wrote:
>> If your application encounters an NSException, then the state of
>> the AppKit, Foundation, and CoreData are undefined. NSExceptions
>> are thrown for non-recoverable runtime errors.
>
> So far I've had fairly good luck catching NSException so I can
> report errors when a document can't be read (e.g. the mythic
> NSInvalidArchiveOperationException). Seems like a recoverable error
> to me...
>
> But I'm not using C++ in this app, and I'm catching fairly close to
> the throw.
Sent from xcode-users to Cocoa-dev.
David is correct... it is recoverable in that the app isn't dead.
However, the NSDocument that failed to read is now in an
unrecoverable state....
b.bum
| Related mails | Author | Date |
|---|---|---|
| No related mails found. | ||






Cocoa mail archive

