Should we eventually improve catch&throw semantics?

On the other hand, at least in my experience, the name throw may discourage its use for non-local returns, but at the same time, it encourages its use for exceptions. Which is the main problem I usually face: People trying to throw exceptions using throw as they do in Java, C#, etc., instead of using error, raise, or exit (which are the ones meant to be used for that in Erlang).

4 Likes