Non-fatal errors in frameworks - how should they be noted?
Non-fatal errors in frameworks - how should they be noted?
- Subject: Non-fatal errors in frameworks - how should they be noted?
- From: Wade Tregaskis <email@hidden>
- Date: Wed, 28 May 2003 22:13:38 +1000
What's the best way to make notice of a non-fatal error within a
Foundation-based framework? At present I'm returning nil's where
appropriate, and outputting via NSLog the reason for the failure. Is
there a better way, other than NSLog, to allow developers to determine
what's going wrong, without killing the program outright? I don't like
using the standard console as my dumping ground for error messages, but
otherwise it has all the features I like - displays in Project
Builder's console when debugging, doesn't kill the app, doesn't require
the returning of error conditions (bad form in Cocoa), doesn't require
exception handling (many people, including myself, don't like to use
exceptions), etc.
I'm contemplating writing my own general logging routine, to log to a
different file. But then that's heading away from well-established
convention, which I'd rather not do unless I have to.
Wade Tregaskis
-- Sed quis custodiet ipsos custodes?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.