Quote:
Originally Posted by xpi0t0s View Post
The destructor is called automatically when you delete the object, but calling the destructor itself does not free the object.

You mean, when we call a destructor explicitly, the object is not freed !?!?!

Is that true ? I think we can explicitly delete the objects by calling destructors.

Quote:
Originally Posted by xpi0t0s View Post
Also depending on the implementation, destroying an object might not actually change the contents of RAM.
But the memory is marked "unallocated", though not changed.

Quote:
Originally Posted by xpi0t0s View Post
So you could access memory after it has been freed, but not reliably because this memory is then available for other code to allocate.