Categories:
.NET (357)
C (330)
C++ (183)
CSS (84)
DBA (2)
General (7)
HTML (4)
Java (574)
JavaScript (106)
JSP (66)
Oracle (114)
Perl (46)
Perl (1)
PHP (1)
PL/SQL (1)
RSS (51)
Software QA (13)
SQL Server (1)
Windows (1)
XHTML (173)
Other Resources:
Why is catch(Exception) almost always a bad idea?
Why is catch(Exception) almost always a bad idea?
✍: Guest
Well, if at that point you know that an error has occurred, then why not write the proper code to handle that error instead of passing a new Exception object to the catch block? Throwing your own exceptions signifies some design flaws in the project.
2014-02-24, 2351👍, 0💬
Popular Posts:
What is the difference between delegate and events? ã Actually events use delegates in bottom. But ...
How To Enter Characters as HEX Numbers? - MySQL FAQs - Introduction to SQL Basics If you want to ent...
Explain all parts of a deployment diagram? Package: It logically groups element of a UML model. Node...
What is CMM and different levels? explain? The Capability Maturity Model (CMM) is a process capabili...
. How can a servlet refresh automatically if some new data has entered the database? You can use a c...