why destructor is not over loaded?
Answers were Sorted based on User's Feedback
Answer / ramakant
Normally (in fact almost always) you never explicitly call
the destructor, it is automatically called by the C++ frame
work when the object is deleted/goes out of scope.
Therefore you would not need to overload the destructor
because the frame work always calls the default destructor.
Additionally the C++ standard defines that a conforming
compiler only allows for 1 destructor per class.
| Is This Answer Correct ? | 21 Yes | 2 No |
Answer / test
Destructor is not over loaded because OOP you can't Invoke a
call of the destructor (Dispose is another thing)
| Is This Answer Correct ? | 12 Yes | 3 No |
Answer / varun
Normally you never explicitly call
the destructor, it is automatically called by the C++ frame
work when the object is deleted/goes out of scope.
Therefore you would not need to overload the destructor
because the frame work always calls the default destructor.
Additionally the C++ standard defines that a conforming
compiler only allows for 1 destructor per class.
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / gyana
In c# we cannot over load the desructor as because
destructor is presented by defaultly in c# and we cannot
create any object of it.we cannot also define a new
desructor.It cannot be explicitly used.for this reason we
cannot invoke the desructor and it cannot be overloaded..
| Is This Answer Correct ? | 3 Yes | 1 No |
Answer / m.salah
destructor not overloaded because not has parameters
| Is This Answer Correct ? | 9 Yes | 12 No |
what is virtual destructor
What is encapsulation process?
Why is static class not inherited?
Write a program to multiply 3x3 matrics
Get me a number puzzle game-program
what is the difference b/w abstract and interface?
2 Answers Merrill Lynch, Schneider, Scio Healthcare,
string is a class or data type in java?
advantage and disadvantage in c++>>oops and what are the questions ask for interview in c++>>oops. could you tell me or reply me
Question In a class, there is a reference or pointer of an object of another class embedded, and the memory is either allocated or assigned to the new object created for this class. In the constructor, parameters are passed to initialize the data members and the embedded object reference to get inialized. What measures or design change should be advised for proper destruction and avioding memory leaks, getting pointers dangling for the embedded object memory allocation? Please suggest. Question Submitted By :: Sunil Kumar I also faced this Question!! Rank Answer Posted By Re: In a class, there is a reference or pointer of an object of another class embedded, and the memory is either allocated or assigned to the new object created for this class. In the constructor, parameters are passed to initialize the data members and the embedded object reference to get inialized. What measures or design change should be advised for proper destruction and avioding memory leaks, getting pointers dangling for the embedded object memory allocation? Please suggest. Answer # 1 use copy constructors 0 Shanthila There is something to be taken care in destructor, in copy constructor, suppose the memory is assigned to the embedded member object pointer with the parameter passed value, but if some other objects of different class also are pointing to this memory, then if some one deletes the object then this class member pointer object will become dangling, or if the object is not deleted properly then there will be memory leak. Please suggest the design change required to handle or avoid this situation
Which is better struts or spring?
What does the code "cout<<(0==0);" print? 1) 0 2) 1 3) Compiler error: Lvalue required
Difference between over loading and over ridding?
12 Answers CTS, Patni, Softvision Solution,