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.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 programming

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.
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-11-10 : 07:39:38
this goes straight to all time favorite comupter jokes


Go with the flow & have fun! Else fight the flow
Go to Top of Page

DonAtWork
Master Smack Fu Yak Hacker

2167 Posts

Posted - 2005-11-10 : 08:01:41
Lies. Its because we are all misanthropic.

Help us help YOU!
Read this blog entry for more details: http://weblogs.sqlteam.com/brettk/archive/2005/05/25.aspx

*need more coffee*
SELECT * FROM Users WHERE CLUE > 0
(0 row(s) affected)
Go to Top of Page

madhivanan
Premature Yak Congratulator

22864 Posts

Posted - 2005-11-10 : 08:04:37
The answer lies in the meaning of Fatal

Madhivanan

Failing to plan is Planning to fail
Go to Top of Page

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.
Go to Top of Page

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
Go to Top of Page
   

- Advertisement -