It is not redundant. In the demonstration, indeed it may appear so, however consider what happens if I want to throw an exception from the end-implementation. I would be throwing an Exception, and not an EmberException.
As well, I find it good practice to catch Exception if there is a chance it MAY be thrown.
Additionally, so far as I know, every derived Exception class has to extend Exception. Correct me if I'm wrong, but I do do believe that is the case. It's all about the polymorphism.
Finally, I should note that I am further developing this implementation (of course). All that array crap is going to be garbage soon. Ugly, and resource intensive.
Does your EmberException extend Exception? If so, remove the catch( EmberException ) block as it is redundant and not needed. EmberException would be of type Exception. ;)
Not enough time to do something productive I run out of ideas Too hard to show people my creations Everything i do has too many errors, and it's too hard I don't get bored!!!
please login to cast your vote and see the results of this poll