For all my experience with the
catch paradigm, I've never seen a situation where I wanted a name error in the
try block to be caught. It's hard to imagine one. A name error is a typo 99% of the time, and a mistake 99% of the remainder. Catching it accidentally can lead to an especially frustrating debugging experience.
So why do all the dynamic languages have
catch statements catch name errors by default?
catch clauses that catch different kinds. But both of them still include name errors in a bare
And their designers obviously realized that there are some exceptions you don't usually want to catch, as they have a class you can catch that's only the things you'd normally want to:
StandardError in Ruby,
Exception in Python (with
BaseException being the real progenitor). But for some reason both of them consider
NameError a subclass of this!
Why do they do all this? And are there dynamic languages that don't?