dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Java Language
Expertise: Beginner
Jun 13, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


All-Encompassing Try

Question:
I was told that in order to make my program easier to read, I should use try to cover all of my program, then catch every exception at the end of the program. Does this make any sense?

Answer:
You should catch exceptions where you intend to handle them. It makes no sense to catch exceptions only at the end of a program when many exceptions are recoverable. For example, network servers need to be able to recover from network I/O errors. You can only do this if you catch exceptions at the point of an anticipated failure point. But you must ensure that you take proper fault-recovery steps. Only fatal and non-recoverable exceptions resulting in the termination of the program should be caught at the end of the program.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date