Can you overload a destructor

Hi Banfa , Can we overload destructor? If yes then plz provide an example? If not then why? Follow Post Reply. What was that dhirajrane? I didn't mean the general constructor and destructor. It was overloaded destructor whether we can define more than one destructor in a class or not?

Why would you need to delete something in more than one way? I don't see why it's necessary. Besides, you could always call a single destructor, and conditionally execute whichever destructor you wish. Banfa 9, Expert Mod 8TB. Therefore you would not need to overload the destructor because the frame work always calls the default destructor. Thanks all of u. Now an objectioct might require various attributes to be assigned during construction.

So Constructors are overloaded very often and it is very common programming practice. Destructor is designed to free allocated memory and do clean up operations. There is no need to take arguments or rather there is no need for overloading.

An overloaded destructor would mean that the destructor has taken arguments. Neither the compiler nor the run-time system make any attempt to check whether you did this right. You have been warned. You are also solely responsible for destructing the placed object.

This is done by explicitly calling the destructor:. But how can we later delete those objects correctly? A pointer to any X allocated anywhere can be assigned to p1. If an Arena keeps track of what objects it holds, you can even write destroy to defend itself against mistakes.

You never need to explicitly call a destructor except with placement new. They are destroyed in the reverse order they appear within the declaration for the class. Base classes are destructed after member objects. In the event of multiple inheritance, direct base classes are destructed in the reverse order of their appearance in the inheritance list.

Note: Order dependencies with virtual inheritance are trickier. See this FAQ for details. Starting with a simple memory allocator function, allocate , you would use placement new to construct an object in that memory. In other words, the following is morally equivalent to new Foo :.

Each of these memory pool objects will allocate a big chunk of memory using some specific system call e. Your memory-pool class might look something like this:. Now one of your users might have a Pool called pool , from which they could allocate objects like this:. Simply because an object cannot be destroyed in one way or another, it should be destroyed completely anyway!

CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance. Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.

Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.