Either use smart pointers, or use a language like C# or Java that has built in garbage collection. Bolting a GC into C++ just seems dumb... defeats the purpose of c++.

Edit:
@ATC: Damn! Ninja'd! I should have read the whole thread.

I must've missed something; not sure what you mean! Explain? XD

In the rest of your post though, I'm assuming these are the Boost libraries you're talking about? I don't know much about Boost but this was a very interesting and informative post.

[quote name='Kyall' timestamp='1349915984' post='4988910']
Edit:
@ATC: Damn! Ninja'd! I should have read the whole thread.

I must've missed something; not sure what you mean! Explain? XD

In the rest of your post though, I'm assuming these are the Boost libraries you're talking about? I don't know much about Boost but this was a very interesting and informative post.
[/quote]

You described the reference counting ( shared_ptr ) & then using some form of memory heap solution. I'd use static memory for short lived things, but not a heap allocation thing like that. Code that should crash shouldn't not crash; which is the problem I have with same static heaping and custom heap manager things.

Not boost, TR1, so technically boost. Since boost became the TR1 extensions library. The difference is that TR1 is part of the cx11 standard, and boost is something people keep referencing as a solution to some one's problem when it doesn't actually apply to the person's problem.