3 ms·
I mean the lesson I'd take from that is "don't use a buggy compiler". If you can't trust your tools then it's very hard to make something you can trust with the
by lmm 4y ago
I mean the lesson I'd take from that is "don't use a buggy compiler". If you can't trust your tools then it's very hard to make something you can trust with them. That changing the code means it compiled in an incorrect way that your test case happened to hit doesn't mean the previous version of the code was being compiled correctly, or was correct code.
- jrochkind1 4y agoI mean, I guess "don't produce or use buggy software" is good advice, depending on what function you're looking advice to do.
- rob74 4y agoThe lesson I take from this is to steer well clear of historic languages with the many intricacies and interdependencies described in the blog post. I assume that there is a reason why that old buggy compiler version is still in use - probably some legacy library or code that only works with that version of the compiler and that nobody has touched for 20-30 years and nobody wants to touch?
- shusaku 4y agoI’m defense of FPS 4.0, plenty of modern Fortran compilers have bugs too…
- Jeff_Brown 4y agoThe best defense being a good offense.