Thread: Memory leak prevention methodogies

Originally Posted by Bubba

Sorry but that is not my methodology or line of thinking about the design of my code. I know how to properly use memory and understand intimately the lifetime of my objects. Therefore whether I use heap objects or stack objects is purely a moot point. Every C++ programmer should understand how to use the heap. If you understand the heap and understand how to properly use it, I see no issues.

I do not follow a general rule of AVOID heap objects. Everything is a tool and I just use the right tool at the right time for the right task.

Sure, you can use heap objects whenever you want, but you can't escape from the fact that when you do, you'll also be introducing potential bugs in your code, beucase those objects must be freed, whether you like it or not.
So in essence, if you avoid heap objects, you don't need to free. Simple as that.
It's a good way to avoid leaks, but it's up to everyone to or not to follow the rule.

Yeah well to each their own. And brewbuck.........what?