UPDATE: I use more C++ now. Now I am checking how to debug containers. I miss the simpler error messages you get in C. Somehow I feel C and C++ are very different languages.
I was reading about dieharder, a test suite for random number generators that I guess I should start using really soon (avoiding the deprecated diehardc which is not maintained anymore).
Anyway, in the same website I found this link:
And I think it's a good read with a nice (probably fictitious) interview to Bjarne Stroustrup.
I stopped using C++ about 6 years ago under the influence of Azul, and I really find it hard now to use C++ (more annoying than hard). I must admit that in the beginning and after being a 5-year C++ user I thought he was crazy for not using C++, but then I tried and I found C code easier to read and more pleasant to write.
I'll use it with no problems if I have to or if I'm part of a team who prefers C++. I will make my best effort. I guess this will often be the case in emQbit. We often do low level stuff and the only options are C and C++ (C being preferable sometimes because of better compiler support).
Of course, some might argue that templates are good and that the STL being part of the language is a good thing that saves a lot of time. And I won't argue on that because it might be true.
And perhaps the answer is to write small modules for Python in C or in C++ and use Python to use the functionality. It will allow you to be more productive IMHO. Scheme is also an option, but it's harder than python for most (python also has more modules).
As usual, it depends.
Perhaps it's silly to write about topics that often end up in flame wars. Finding a similar line of thought in the web page of someone that many consider an expert in the High Performance Computing field motivated me to do so.
Discussion (2)Last update: 2008-05-04 (Rev 14092)