For the high performance stuff I write my kind of restrained C++: never STL in the interfaces of the "modules," use STL algorithms (they are good) but otherwise manage memory in custom ways (which is easier by not using STL containers!).
But I had to solve one interesting problem using some recursive definitions and code, and discovered that once I "freed" the code from classes (made them C functions) I was able to express it properly -- just having them as members prevented me to see that the solution is much more obvious when you actually use plain pointers and don't think about the same "object" even during the life of the function. Add to that in the member "this" can't be null.
When you need real expressiveness, C can't be beaten. C++ syntactic sugar helps sometimes, but limiting to it is... limiting!
But I had to solve one interesting problem using some recursive definitions and code, and discovered that once I "freed" the code from classes (made them C functions) I was able to express it properly -- just having them as members prevented me to see that the solution is much more obvious when you actually use plain pointers and don't think about the same "object" even during the life of the function. Add to that in the member "this" can't be null.
When you need real expressiveness, C can't be beaten. C++ syntactic sugar helps sometimes, but limiting to it is... limiting!