Re: Try/Catch

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

A bug in the editor should result in a crash, and the developer should correct the bug. If possible, the reason for the bug should be communicated to the user, but regardless if an incorrect result can occur then the user is better served by a crash then by the output of incorrect data.

So it's better that I lose all my data, and be protected from an exception I could possible recover from?

What if the data were a 15 minute recording?

From a UI perspective, a program crashing is never the correct thing to do.

If the developer wrote bad code, then yes, that is the correct behavior.

dcuny said...
jaygade said...

I'm not sure that your example is valid.

So an example that happened to me isn't valid?

- David

It did seem contrived. If it happened to you, then the one to blame for the fault is the developer, not the language.

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

Search



Quick Links

User menu

Not signed in.

Misc Menu