Bad things about C++

Since the python thread was a smashing success, it's only logical to have a C++ equivalent. So list the bad things about C++. Constructive thread, please. I will get the ball rolling:

 * Segment faults.
 * Broken standard library.
 * One word, the forced indentation of code. Thread over.
 * Broken templates.

>>122
So in other words, you have no control over when the gc executes?

If you are working with a project with rather large ammounts of data that needs to be moved, executed or computed and you have a limmited ammount of memory, a gc could acually ruin your whole project, since it would have no idea of what data to 'free up', and might thus free up a hunk of memory that was in use, or had some other purpos.

You can of course write your program with the GC's in mind, but that would generaly slow the program down.