It’s good to know what’s good coding practice, what’s not, and why it isn’t… but part of the beauty of C++ is, that it will LET YOU if you REQUIRE such actions.

Calling the default destructor directly does not remove the object from the heap. It just makes sure the object’s destructor code is run. The actual deallocation of heap memory is up to you. In this example I’ve allocated the memory block with a simple “malloc” which means I can only deallocate it by calling “free” on the complete block. Other actions will cause heap-corruption.

As I said in the beginning, it’s a more advanced topic… there’s a lot that can go wrong here

I’ve corrected some character problems caused by wordpress. The sample code should compile now, and you can use it to make your own Foo class and see the destructor get called.

Good luck!

According to C++ practice, it is not good to explicitly call destructor directly. Do you have alternate solution to remove the object from the heap? BTW, do you have a sample code to show that the deletion of object is working?

THanks @!