I wonder what abuse of C++ templates you are looking at, as for myself I find the ATL library particulary abusing of C++ templates.
The author of the atrocity had obviously heard that templates were "efficient", so they implemented their little (little - hah!) stream reading class with templates.
Except there was a bunch of different behaviour depending on the object so they were continually checking objects typeid() to decide what to do in an massive evil switch statement, which triggered off what looked (after considerable pondering) like the guts of some kind of expression template. Which would be fair enough if there were any chains of expression to optimise out. Since there aren't it's a couple of hundred lines of fardling no-op.
The most annoying thing is that it's a massive case of the first law of optimisation (i.e. "don't"). The stuff this monstrosity deals with doesn't happen often, it's running on a machine with oodles of memory, it's taking data of the net and a database so the bottleneck is definitely not the code, etc.
Not to mention the fact they invented there own string class! Twice! Use templates badly and then ignore the STL. Fantastic.
If they'd just written it as plain C++ classes with sensible use of the STL it would be a quarter the size, work just as well and be perfectly obvious code.
I'm going to go write some Ruby so I can feel clean again :-)
|