is throwing exception from a constructor not a good practice ?
- 5 Answers
- 9611 Views
- Ericsson, I also Faced
- E-Mail Answers
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 |
What is c++ redistributable?
What are special characters c++?
What is virtual constructor paradigm?
Define precondition and post-condition to a member function?
What are the storage qualifiers?
Which bit wise operator is suitable for turning off a particular bit in a number?
When does a 'this' pointer get created?
make a middle node of doubly linklist to the top of the list
What is istream and ostream in c++?
How to declare a function pointer?
What is cloning?
What are its advantages and disadvantages of multiple inheritances (virtual inheritance)?
STL 
