Interested to Buy Any Domain ? << Click Here >> for more details...
is throwing exception from a constructor not a good practice ?
- 5 Answers
- 11227 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 |
Where must the declaration of a friend function appear?
What is the use of ‘using’ declaration?
What's the order in which the local objects are destructed?
How would you implement a substr() function that extracts a sub string from a given string?
Is c++ the best programming language?
What is "mutable" keyword?
What does n mean in c++?
What is size of a object of following class? class Foo { public: void foo(){} }
Is map ordered c++?
What is the advantage of an external iterator.
How does list r; differs from list r();?
Is it possible to write a c++ template to check for a function's existence?
STL 
