OpenEuphoria

Re: How to handle crashes?

• Posted by draegur at comcast.net May 31, 2003
• 433 views

I have seen many people here comment on my original question about crash 
handling/error trapping. Several of you have said there is no excuse for 
"crud" programming. Now, everyone is entitled to their opinion, but why 
should it matter to you how I program? The smallest file I have in my 
mud is 15,000 lines of code. There are many ways that new code I add 
interacts with old code that perhaps I wasn't expecting and *poof*, 
there goes anything they've done since the last backup of the database.

Why is it so wrong for a language like euphoria to allow me flexibility 
in programming? Perhaps someones program to keep track of bank accounts 
might not benefit from being able to keep their programs running, but 
for someone doing a project like I am it's almost a nessessity.

You've all had your chance to rant about how it should be handled like 
this so as not to encourage "crud" programming, or how it should not be 
done at all because it will encourage "sloppy" programming. My rant in 
response is, why do you care how I code? If using the print() command 
could lead to people being lazy, would you not include it because of 
that? So what if you don't need something to handle errors as I do? 
Unless, of course, the only reason why you do not write "sloppy" or 
"crud" code is because you cannot?

There. I feel a little better now.

(These comments were not directed at everyone, just those few on their 
personal little soap boxes)