Exception handling is one of those programming techniques that beginners often neglect to implement. However, when they end up working on a large project on which dozens of other colleagues are working, they find that you just can’t afford to be superficial. Throughout this article we’re going to cover exceptions, explain what they are, how to work with them, and why they are important—ultimately, how to handle them.
Slowly but surely we've arrived at the end of this article. This means by now you've learned about exception handling. During this article I tried to focus mostly on practicality and explain those concepts that are especially important, while trying to prove why they cannot be neglected. Exceptions must be handled, period.
We all know that whether checked or unchecked, programmers ought to deal with exceptions, otherwise abnormal program termination may occur, and this problem must be minimized. No one can rely on, for example, the user never typing in the wrong data. The user can be pretty dumb... jokes aside, you get the idea!
As always, we stress the fact that theory without practice is barely worth anything. Ultimately, it's up to you to deepen the knowledge presented here. And to be honest, what I covered in this article is barely the tip of the iceberg, though, the basics are spilled out. There are entire books written on the subject as well as very well-thought-out and prestigious documentation on exception handling. Check them out.
In closing, I'd like to invite you to join our experienced community of technology professionals on all areas of IT&C starting from software and hardware up to consumer electronics at Dev Hardware Forums. As well, be sure to check out the community of our sister site at Dev Shed Forums. We are friendly and we'll do our best to help you.