Home/ Questions/Q 7430631
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-29T09:10:23+00:00

I was reading this question Does calling a destructor explicitly destroy an object completely?

  • 0

I was reading this question Does calling a destructor explicitly destroy an object completely? where this situation comes up in code.

Object* aWidget = new Widget(); //allocate and construct
aWidget->~Object();             //destroy and DON'T deallocate

From the answers, I undrestand that the memory region is in fact not deallocated in this situation. My question is (more out of curiosity than anything):

How can I delete the memory pointed to by aWidget after the two lines of code above have executed? I would assume calling delete aWidget; would fail because it would try to run the destructor on an already-destructed object. Could you call free(aWidget) or something like that instead to just target the memory?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    free would, factually speaking, be my best guess. However I don’t think you can do anything without invoking UB. How did you arrive at a requirement to invoke the destructor like that?

    • 0