Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As we all know, when a function returns, stack-allocated objects would be reclaimed and the associated destructors would be invoked before that. My question is: how is a memory location determined to represent objects so that we can call the destructor? And is there any run-time overhead incurred to do this?
Memory location does not determine when the constructor gets called. The compiler knows which variables are allocated on the stack and creates the appropriate code to call the corresponding destructors.
At least, they are normally on the stack. The point is the same logic could be used regardless of where the memory was stored. Being stored on the stack simply means that they need to be called one way or another.