Re: Try/Catch

new topic     » goto parent     » topic index » view thread      » older message » newer message
Ekhnat0n said...

I add at all new stages of programming a distinct ErrNo (or ExeptNo) telling me exactly where I went wrong whenever that happens, so I can correct the code tested immediatly.

try/catch It doesn't replace good coding practices.

But once the code is released, the end user is no longer the developer.

Users aren't beta testers, and shouldn't be treated as such.

The goal once the program is in production is to protect the user's data, and give them a fault-tolerant experience, as far as possible.

Writing solid code is key to reducing errors.

But there will be exceptions, and it's completely unacceptable to users that their programs crash and display error codes when that happens.

- David

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

Search



Quick Links

User menu

Not signed in.

Misc Menu