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, 2338👍, 0💬
Popular Posts:
What is hashing? To hash means to grind up, and that's essentially what hashing is all about. The he...
If client side validation is enabled in your Web page, does that mean server side code is not run? W...
Explain in detail the fundamental of connection pooling? When a connection is opened first time a co...
What are secure and non-secure websites? A secure Website uses the Secure Socket Layer (SSL) protoco...
Why is it preferred to not use finalize for clean up? Problem with finalize is that garbage collecti...