Why is it a bad idea to throw your own exceptions?
Answers were Sorted based on User's Feedback
Answer / supratim sengupta
Actually throwing your own exceptions is an excellent way
to handle various exceptions the way you want it to handle.
You can centralize the whole exception handling. It could
be useful in product development where you might miss out
some exception conditions and then you can always write a
common custom exception handler that can shoot you an email
with all the details of the exception.
Is This Answer Correct ? | 8 Yes | 1 No |
Answer / guest
Not necessarily. If you're writing a library of code to be
used by other clients you don't always know the right thing
to do if an exceptional problem comes up. So it isn't always
a bad idea to throw your own exceptions.
Is This Answer Correct ? | 5 Yes | 2 No |
Answer / 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.
Is This Answer Correct ? | 3 Yes | 1 No |
Answer / japan shha
Perhaps what you meant to ask was "When is it not necessarily a good idea to throw my own exception?"
http://stackoverflow.com/questions/2215112/why-is-it-a-bad-idea-to-throw-your-own-exceptions
Is This Answer Correct ? | 0 Yes | 0 No |
What is the use of 'as' Keyword in C# ?
What are the Types of optimization and name a few and how do u do?
How are delegates chosen?
Can firstordefault return null?
What does dbml mean?
What?s a satellite assembly?
What is the use of "default" and "Using" keyword?
Is c# substring zero based?
Explain the process of polymorphism with an example?
How long has c# been around?
What is the partial class in C# What is the use of partial class in C#?
What is the difference between list and array in c#?