|
|
Back to UserFriendly Strip Comments Index
|
errors | by perldude | 2006-11-19 12:55:59 |
|
That last statement... | by HadEnuf | 2002-06-11 13:34:49 |
| Said what I meant, meant what I said |
by perldude |
2002-06-11 16:58:29 |
I said and meant "Most errors that shouldn't have been caught earlier aren't really errors". Obviously I need to clarify. What I meant was that if it's not fatal, and if it's OK to have gotten to that point, it's not so much and error as an expected situation (an "expected error" though I've never cared for that phrase). For example, suppose the line in your code opens a file. There are three things that could happen:
- You succesfully open the file. Everybody is happy.
- You can't open the file, you don't know you could have gotten this far without getting the name of a known-to-exist file, so you just die
- You can't open the file, but that's not fatal because your file open command was also a way to check if the file really exists. I.e., it's ok that things went this far without checking for the existence of the file... it shouldn't have been caught earlier. So you display a message, return false, or do whatevr the program is designed to do in that expected situation. I.e., it's an error in the sense that it might not be what the user hoped to happen, but it's within the parameters of what you the programmer were ready for.
|
|
[ Reply ] |
|
To put it more simply... | by Schol-R-LEA;2 | 2002-06-11 21:54:43 |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|
