Constructor call with malloc?
AP, I dont meen for him to change the behavior of new and delete to something other than allocating memory. If he wants to ensure that malloc is used when new is used all he has to do is overload new and delete to allocate with malloc even though that's what the default behavoir should already be. There are no maintenence costs with overloading new and delete, that's why they exist and the best way to get with the language would be to use its more powerfull features (operator overloading and the like) to make his code easier to use.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement