| |
| | Server clinic: Writing good exceptions |
 | | The first step in using exceptions in a particular development project, therefore, and much the most-neglected one, is to determine your program's requirements for exceptions. |
 | | When catching exceptions, then, be certain you get all of them, be precise in how you do so, and use the information available in your chosen language to synthesize useful output. |
 | | There's a great deal more to know about exceptions, very little of it adequately detailed in printed books: guarding exceptions so they can't be used to breach security; exception metrics; performance consequences of exception design; ways to debug, benchmark, and validate exceptions; exceptions and resource management; and much more. |
| www-106.ibm.com /developerworks/linux/library/l-sc13.html (2014 words) |
|