is throwing exception from a constructor not a good practice ?
Answers were Sorted based on User's Feedback
Answer / vikas sood
throwing exception from a constructor is not bad at all. It
is actually advised to use exceptions when you fail to
create your object properly due to any reason. In this case
memory will not be allocated for the object and no
destructor will be called.
Is This Answer Correct ? | 11 Yes | 1 No |
Answer / manjunath
Throwing a exception from constructor is perfectly good
habit. That is how to handle errors in the constructor.
Smart pointers can also be used in this scenario.
Is This Answer Correct ? | 4 Yes | 1 No |
Answer / dps
ya its better i think because it will take less memory and
less time
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / shwetha.v.g
Actualy though when an object is created memory will b
allocated but the process of allocation of memory will be
complete only if conytructor is successfully invoked so if
constructor throws an exception memory will not be
allocated for that object.
Is This Answer Correct ? | 1 Yes | 6 No |
Answer / saranya
yes, because constructor does not throws an exception
Is This Answer Correct ? | 1 Yes | 8 No |
Will rust take over c++?
What is the best c c++ compiler for windows?
Why is c++ still used?
Write a program using GUI concept for the scheduling algorithms in Operating system like SJF,FCFS etc..
What does '\r' and '\b' mean? Please explain with example.
Describe about storage allocation and scope of global, extern, static, local and register variables?
Write a function which takes a character array as input and reverses it in place.
2 Answers Lehman Brothers, Vision Infotech,
What is difference between class and structure in c++?
Define the process of error-handling in case of constructor failure?
What things would you remember while making an interface?
Why do we need runtime polymorphism in c++?
Write a note about the virtual member function?