I've been totally conversed back to "C" from "C++" after working on a port of Metal Gear Solid to PC in 2000. I've had no problems understanding and reading thr

I've been totally conversed back to "C" from "C++" after working on a port of Metal Gear Solid to PC in 2000. I've had no problems understanding and reading through the code the Konami developers have written, it was using some kind of generic OO system in "C" with TCL-like passing of arguments (object* obj, int argc, const char*argv[]) - and passing text messages. Yes that was okay even on Playstation1 I guess. Now I still prefer C++ at work for certain things as I'm simply too lazy to do it correctly in "C" - give me STL, Qt, any UI framework written in there, and it's easier to use. But for core/system libraries (zlib, png, jpeg, tiff, zmq, libpq, etc.) I'd rather have it in "C", at least on the interface part, but I've seen what hiding of C++ or .NET can do with a crazy debugger :)