True, but then again by that argument I could also say that any JavaScript programmer can do anything that a good C++ coder can do. Not that I'm beating on JavaScript, I actually quite like the language. The point is that you could substitute any language. Performance isn't everything. Java actually fixes quite a few problems discovered in C++ :-)
Microbenchmarks are pretty meaningless anyway, but MSVC is far from being the final word in compiler technology. Again, if performance were everything then I'd better go learn me some (more) Fortran.
Excellent, I was wondering when you'd move on to talking about SmallTalk! ;-)
*Ahem* I'm pretty sure "those" days that you refer to were quite a bit before your time! The world of computers was very different back then, I just can't see how this is a relevant point.
Well now if Pascal has a monopoly on bug free code I'm sure there's quite a lot of academics that would like to know more! Think of the defence industry and how much money they could save with bug free software!! More seriously, let's get real - Pascal's type system isn't revolutionary. It's good enough though, I'm not beating on it.
There's quite a lot of case-sensitive languages ... I guess, programmers just find naming things hard?
I can honestly say that I've never come across this kind of bug. Maybe it is a learned discipline, I don't really know, but I think you might be making a mountain out of a molehill.
I'm not too sure about that, there's just the C standard library for strings, and the standard C++ string container. Also, C++11 has standard unicode string support (hooray!).
Why would you want to do that if C string handling is so bad?
Aw come on that's kids stuff. Everyone knows pre-increment is write then read. If you really want to go down the rabbit hole (I know you don't) then you would have pointed out that two increments in the same statement is undefined behaviour.
That's it, I'm going to learn me some Ada!
Bookmarks