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.
I recently read a lot about “preventing heap allocation for a class” (see this question).
I was able to understand “how”, but now I can’t figure out “why” someone would like to do that.
I guess there must be legitimate reasons for this, but I just can’t figure them out.
In short: “Why may I want to forbid users from creating objects of my class in the heap ?”
Some classes make sense only if the objects are instantiated on the stack. For example, Boost scoped_ptr, or lock_guard.