Sure would stop illegal right-on-reds though! (Sorry it was just a great image...)
-----Original Message----- From: Steven H. Schwartz [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 08, 2001 1:25 PM To: Palm Developer Forum Subject: Re: Why fatal error message? "Peter Epstein" <[EMAIL PROTECTED]> wrote in message news:67388@palm-dev-forum... > > While I heartily agree that if the docs say is returns an error code it > should do just that, I take exception to the ideal of returning error codes > rather than giving fatal errors. The problem with error codes is that it's > all too easy to forget to check for them, and this can lead to latent bugs. > By catching bugs early, the developer is freed from having to back-track to > figure out what went wrong. This is straight out of the book "Writing Solid > Code". Peter, You're right -- it's easy to ignore returned error codes. However, signalling fatal errors makes it significantly more difficult to debug, especially if you are debugging a non-connected handheld, e.g., a Clie (which CW8 still wont talk to) or IR operations. Using "fatal" screens is like highway patrolmen shooting out the car tires rather than citing the driver for an illegal right-on-red. I'd rather have access to a descriptive explanation of the problem. --Steve -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
