Keith Rollin wrote:
>Well, if you weren't programming around the ErrFatalDisplayIfs, then you'd
>spend your time programming around random system crashes, and without the
>benefit of an error message telling you what went wrong.
I have to disagree with you on this. It is inexcusable that the documents
indicate a function returns an error when in fact it generates a fatal
error dialog. As a result, the current behavior causes me to spend my time
programming around "random system crashes" which the stupid fatal error
dialogs generate.
I wrote my first app to include lots of error checking. As I started
testing all the pathological error cases, I found that my error handling
logic wasn't being called and it just generated fatal error displays. It
took a lot of extra work to figure out how to program around some of these
crazy fatal errors.
It would be one thing if the docs said "This function generates a fatal
error display under these conditions: A..., B... C...". But for it to
generate a fatal error display when the docs say it will return an error
code is outrageous.
Bill
