Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Bad things about C++

Name: Anonymous 2007-02-09 4:03

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.

Name: Anonymous 2007-08-12 22:04 ID:8ezqyssb

>>94
Each to their own I guess, but I find template metaprogramming incredably useful.
Indeed. You're stuck with a poor language, and need to get something done. However, in a decent language you wouldn't need template metaprogamming in the first place.

Template metaprogramming has the following three problems:
a) It indicates just how weak the non-templating part is (what most people call C++).
b) Template metaprogramming and "normal" programming are wildly different. By any sane standard, they are not the same language at all.
c) The metaprogramming part is a horrible and poorly designed functional language. Templates were never meant to be abused this way. SFINAE anyone?

I think of template metaprogramming the same way I think of the C preprocessor: if you're allowed multiple passes C macros are actually Turing complete, but all sane -- and most insane -- developers will say "fuck that" and move on to using a better tool.

You're welcome to continue using C++, but you're wasting your life and developer vitality. If you don't burn out, you'll still eventually realize that developers with other tools have left you in the dust, and had fun the entire time.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List