3 ms·
It's a good discussion of the behind the curtains working of compilers But I'm very aware of "smart code" and we shouldn't be writing code that relies on the d
by raverbashing 13y ago
It's a good discussion of the behind the curtains working of compilers
But I'm very aware of "smart code" and we shouldn't be writing code that relies on the details (especially ones that might change between compilers)
- greyfade 13y agoBut we should certainly be aware both of what the language requires of the compiler and of potential pitfalls.
- waps 13y agoThe problem there is that while compilers have been getting better, they're nowhere near beating good programmers (yet ?). Languages other than C/C++ get in the programmer's way and prevent them from using "maximum" cleverness, and that means the best java/c# programs are simply always going to be slower than the best c/c++ programs.
- dllthomas 13y agoThat's true on balance, which is why C/C++ is still typically faster than managed languages. In many particular cases it's not true, however. Consider "register" or "inline" directives, which have been advisory for a long time.