FROM : Kay Roepke
DATE : Thu Aug 03 23:41:23 2006
On 3. Aug 2006, at 22:55 Uhr, John Stiles wrote:
> That statement may be true, but I really hope Apple wouldn't do
> something like that, because in practice it would result in many
> apps with latent (or not-so-latent) bugs.
Well, the docs are clear about this. In "Error Handling Programming
Guide For Cocoa" it explicitely says in a Note box:
"Note: Cocoa methods that indirectly return error objects in the
Cocoa error domain are guaranteed to return such objects if the
method indicates failure by directly returning nil or NO."
see <http://developer.apple.com/documentation/Cocoa/Conceptual/
ErrorHandlingCocoa/CreateCustomizeNSError/chapter_4_section_2.html>
So, I really think this one is covered well enough. It's a bit of a
different case for OP's question, though even that is mentioned at
the very bottom of the page in the error handling guide.
-k
--
Kay Röpke <<email_removed>>
classdump Software
DATE : Thu Aug 03 23:41:23 2006
On 3. Aug 2006, at 22:55 Uhr, John Stiles wrote:
> That statement may be true, but I really hope Apple wouldn't do
> something like that, because in practice it would result in many
> apps with latent (or not-so-latent) bugs.
Well, the docs are clear about this. In "Error Handling Programming
Guide For Cocoa" it explicitely says in a Note box:
"Note: Cocoa methods that indirectly return error objects in the
Cocoa error domain are guaranteed to return such objects if the
method indicates failure by directly returning nil or NO."
see <http://developer.apple.com/documentation/Cocoa/Conceptual/
ErrorHandlingCocoa/CreateCustomizeNSError/chapter_4_section_2.html>
So, I really think this one is covered well enough. It's a bit of a
different case for OP's question, though even that is mentioned at
the very bottom of the page in the error handling guide.
-k
--
Kay Röpke <<email_removed>>
classdump Software






Cocoa mail archive

