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, 2309👍, 0💬
Popular Posts:
Can you explain Forms authentication in detail ? In old ASP if you where said to create a login page...
How to reduce the final size of an executable file? Size of the final execuatable can be reduced usi...
What is difference between ADPATCH and OPATCH ? # ADPATCH is utility to apply ORACLE application Pat...
What Happens to Indexes If You Drop a Table? - Oracle DBA FAQ - Managing Oracle Table Indexes If you...
What is Traceability Matrix? Traceability Matrix is one of the document will prepare by QA.To make s...