Re: Try/Catch
- Posted by elias_maluko Jan 08, 2015
- 5637 views
- It's not really my place to deny others
- There are real user experience benefits
- There are valid cost benefits (crappy code is part of that)
- There are even performance gains to be had (and hits to suffer)
- If you don't like it you don't have to use it
This. Especially #5.
+1000
On the other hand, if you want Euphoria to be your own private language, by all means don't implement features common to other languages, and then tell people that Euphoria is superior because it lacks these features. And be sure to cast aspersions on their coding skills while you're at it.
- David
Note that once you introduce something like exception handling in a language, its not a optional thing. Many situations will force, even the developers that dont like it, to use it.
For example: If the fopen() function throws a exception (instead of a error code) when a file dont exists, all developers are forced do write try/catch blocks to check if everything is OK.
Exception handling is not this holy grail you're selling. The same way code can break with a error, it will break with unhandled exceptions.
I dont like exception handling, and think that its not compatible with anything that uses simplicity as a feature (my personal opinion here).
Sorry my bad english...
