Re: How to handle crashes?

new topic     » goto parent     » topic index » view thread      » older message » newer message

On Sat, May 31, 2003 at 01:32:37PM -0400, draegur at comcast.net wrote:
> 
> 
> 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.
> 

I hereby define crud programming as this:

To continue execution of a program, after what should be a fatal error,
at the risk of corrupting the data that the program works with.

Under that definition, what you want to do is not crud programming.
(Even if you want to back up the db and restart (or resume) the mud server,
its still not crud programming since you aren't risking any corruption.)

> 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.

Agreed. I believe that for games, especially multi-user ones, that sort
of ability is a great advantage. (I also believe someone else who argued
against crud programming said that ignoring errors in games is basicly OK.)

> 
> 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?

That was one of the arguements against goto, you know. ;]

try-catch for euphoria is a must, i feel....

> 
> There. I feel a little better now.

Good for you. ;]

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

HA!

> 
> 
> 
> TOPICA - Start your own email discussion group. FREE!
> 

j. brown

> 
> 

-- 
 /"\  ASCII ribbon              | http://www.geocities.com/jbrown1050/
 \ /  campain against           | Linux User:190064
  X   HTML in e-mail and        | Linux Machine:84163
 /*\  news, and unneeded MIME   |

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu