Summoning Error Classes As Needed

Shades of Gray: Summoning Error Classes As Needed:

StarTrader added about 2 hours later: I like the implementation as a concept, but I am concerned about what the results would be for client code. This would seem to encourage the creation of an arbitrarily large number of Error classes. To my mind the goal of raising an error is to have some other part of the program catch it and do something intelligent to fix it. I, therefore, only create a new error class when I think the error can be handled somewhere. This being the case, I find a list of all potentially handleable errors useful, even if I don't click on them in the rdocs. I guess my question is, why not just raise a RunTimeError or some other already defined Error class and use the properties of the Error class to give more detail?

Full article: http://blog.grayproductions.net/articles/summoning_error_...