Re: Try/Catch
- Posted by dcuny Jan 13, 2015
- 5295 views
Shian_Lee said...
I have nothing against Try/Catch or ON ERROR GOTO or any other approach. I just believe that hiding Try/Catch in the low level and use error codes in the high level, will keep the language simple as it is.
I agree that foreseeable results should return error values, not exceptions.
I also agree that defensive coding is the best approach. Especially with Euphoria, where the sequence is the core datatype.
And relying on try/catch isn't a panacea. If it's triggered, it generally means that some portion of an application failed to execute properly.
That's bad, and needs to be avoided.
By way of analogy: try/catch allows you to keep running on three wheels when a tire has blown out.
- David
