Error Exception handeling

vbboyd · March 12th, 2013, 03:01 PM

When it comes to error trapping is not the common conventionality supposed to be to trap for the least likely to happen to the most likely common error to happen? Or is vice a versa? Is it not supposed to bubble up the error chain in such a manner?

vbboyd · March 12th, 2013, 03:04 PM

Is not error trapping supposed to trap from most generic error to least generic or specifically defined error? How exactly is the hierarchy of error trapping supposed to working if you want to catch for multiple different errors?

vbboyd · March 12th, 2013, 03:08 PM

Quote:

Originally Posted by vbboyd

Is not error trapping supposed to trap from most generic error to least generic or specifically defined error? How exactly is the hierarchy of error trapping supposed to working if you want to catch for multiple different errors?

Also from your own professional perspective how much of a sin is it to allow for the yellow and brown screen of death to pop up in front of an end user on an application that is in use and in actual production?

Imar · March 12th, 2013, 03:31 PM

I always get a bit confused by the way you ask your questions ("is it not... "instead of "is it" or "what is....") but I believe the answer is no.

It's about specific exceptions (SmtpException over Exception), not about likeliness that the error happens. Check out page 682 and further.

Quote:

how much of a sin is it to allow for the yellow and brown screen of death to pop up in front of an end user

Pretty much the biggest sin you can commit. Check out page 6990 and further for ways to prevent this.

Over the past couple of weeks or months I answered many of your questions. I think not once (but I could be wrong) have you followed up on them. Are the answers so clear there's nothing else to ask? Do you think it's a bad forum practice to post a seemingly useless "thanks for that" message or is there something else?

Imar

Thermopyle · March 12th, 2013, 03:42 PM

Imar, just wanted to point out the page number issue here: "Check out page 6990 and further for ways to prevent this."

The book is long, but not THAT long. :)

Imar · March 12th, 2013, 03:48 PM

Heuh? You don't have the super duper special edition with the extended bonus material? ;-)

I meant page 690. Thanks for pointing that out.

Imar

vbboyd · March 12th, 2013, 06:48 PM

Quote:

Originally Posted by Imar

I always get a bit confused by the way you ask your questions ("is it not... "instead of "is it" or "what is....") but I believe the answer is no.

It's about specific exceptions (SmtpException over Exception), not about likeliness that the error happens. Check out page 682 and further.

Pretty much the biggest sin you can commit. Check out page 6990 and further for ways to prevent this.

Over the past couple of weeks or months I answered many of your questions. I think not once (but I could be wrong) have you followed up on them. Are the answers so clear there's nothing else to ask? Do you think it's a bad forum practice to post a seemingly useless "thanks for that" message or is there something else?

Imar

Since you asked....
Sorry. I have attention deficit disorder, and sometimes I forget things (and I also get bored) very easily. Sorry my bad.