in oop lanuage,let us take a look at the key principles of handing the errors or exceptions:
1 do not try to handle system errors ,fail it fast when it happened. try to leave a audit trail of the problem that can be used to troubleshoot it
2 handle the exception as soon as possible,do not let exception to propagate far away from the source。
as we all know, in JAVA world, there are two types of the Exception, checked exception and unchecked exception.
unchecked exception :the defects and bugs in a program,they usually can not be recovered in the runtime.the method is not obliged to establish a policy thrown by its implementation
checked exception: represent invalid conditions in the areas outsides the immediate control of the program . like database problems,network outrage, invalid user input these catchable exceptions. the method is obliged to establish policy thrown by its implementation.
it can be catch and handle ,when it happen.like when the caller invoked the method of API.it need declare the Exception who declared in the API.when the application is not large scale,use checkexception in the few parts ,they are excellent and elegant.but when the application is large scale, when you realized thousands of palces using try catch ,let souce look ugly and cumbersome,so i suggest make the unchecked exception to declare the API rather than catch it in every suspicious places
3 do not use too many try catch statement,it will mess up the source;