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 know Microsoft themselves used to recommend overriding operator new with calls to HeapCreate() and HeapAlloc(), but that was a while ago. See KB139638 for more details.
Would i still benefit from overriding new/delete on Win32? What would be the recommended implementation?
TIA.
The article says you can do it, not that you should. The code in it is so badly written it isn’t funny, and it is not thread safe. In general, the implementation supplied new and delete will work well for all general programming needs. You should only consider re-implementing them if you have identified a specific problem that such a re-implementation would solve.