Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-11-10 : 07:38:20
|
| arlegui writes "why do programmers prefer to have fatal error than non-fatal error?" |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-11-10 : 07:38:24
|
| They're suicidal and can't take the pressure anymore. |
 |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2005-11-10 : 07:39:38
|
this goes straight to all time favorite comupter jokesGo with the flow & have fun! Else fight the flow |
 |
|
|
DonAtWork
Master Smack Fu Yak Hacker
2167 Posts |
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
Posted - 2005-11-10 : 08:04:37
|
The answer lies in the meaning of Fatal MadhivananFailing to plan is Planning to fail |
 |
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2005-11-10 : 08:40:52
|
| I *think* (just a guess here) the statement means that you'd rather have an unhandled exception stop the program from running, forcing the developer to write code to anticipate and handle things that can go wrong, rather than ingoring exceptions and errors completey and having the code always continue. i.e., in VB terms, all of your code surround by ON ERROR RESUME NEXT. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-11-10 : 14:41:42
|
In my case its just "defensive programming"SELECT CASE MyCanOnlyBeYesOrNoColumn WHEN 'Y' THEN 'Yes' WHEN 'N' THEN 'No' ELSE RaiseCriticalErrorBecauseWillNeverHappen_Function() END Kristen |
 |
|
|
|
|
|