http://mjtsai.com/blog/2009/01/06/abstracting-away-from-exceptions/ Sat, 20 Mar 2010 14:01:58 -0700 http://wordpress.org/?v=2.9 hourly 1 http://mjtsai.com/blog/2009/01/06/abstracting-away-from-exceptions/comment-page-1/#comment-465740 Michael Tsai Wed, 07 Jan 2009 18:59:37 +0000 http://mjtsai.com/blog/?p=1849#comment-465740 Have you filed a bug? Have you filed a bug?

]]> http://mjtsai.com/blog/2009/01/06/abstracting-away-from-exceptions/comment-page-1/#comment-465733 Marc Charbonneau Wed, 07 Jan 2009 18:51:36 +0000 http://mjtsai.com/blog/?p=1849#comment-465733 You should see it if you find your Core Data XML file in Finder, and enable 'Locked' in the Get Info pane. I forget exactly what method it is, but one of the Core Data objects throws an exception that comes from the underlying NSData object. You should see it if you find your Core Data XML file in Finder, and enable 'Locked' in the Get Info pane. I forget exactly what method it is, but one of the Core Data objects throws an exception that comes from the underlying NSData object.

]]> http://mjtsai.com/blog/2009/01/06/abstracting-away-from-exceptions/comment-page-1/#comment-465698 Michael Tsai Wed, 07 Jan 2009 17:13:59 +0000 http://mjtsai.com/blog/?p=1849#comment-465698 I don’t recall running into that problem. Do you have an example? I like the Cocoa convention that exceptions are for compile-time programmer errors and NSError is for expected runtime errors that need to be handled. If you’re commonly getting exceptions, that would seem to be either a bug in your code or in Core Data. I don’t recall running into that problem. Do you have an example? I like the Cocoa convention that exceptions are for compile-time programmer errors and NSError is for expected runtime errors that need to be handled. If you’re commonly getting exceptions, that would seem to be either a bug in your code or in Core Data.

]]> http://mjtsai.com/blog/2009/01/06/abstracting-away-from-exceptions/comment-page-1/#comment-465693 Marc Charbonneau Wed, 07 Jan 2009 17:01:01 +0000 http://mjtsai.com/blog/?p=1849#comment-465693 I've always kind of preferred exceptions, but the mix of Exceptions and NSError that exists in Cocoa today needs to go. In Core Data for example, even (somewhat) common error situations can cause an exception to be raised, even though the method itself takes an NSError object as a parameter. I've always kind of preferred exceptions, but the mix of Exceptions and NSError that exists in Cocoa today needs to go. In Core Data for example, even (somewhat) common error situations can cause an exception to be raised, even though the method itself takes an NSError object as a parameter.

]]>