Re:Let's Build a Simple Interpreter, Part 1 (2015)
by the_duke on Monday September 12, 2016 @12:40AM
(#12477231)
Yeah, I think a more appropriate statement would have been "If you don't know how compilers work, you don't know how software works".
Re:Let's Build a Simple Interpreter, Part 1 (2015)
by nickpsecurity on Monday September 12, 2016 @07:40AM
(#12478836)
Again, software in most HLL's that uses compilers. There's assembly, macro assemblers, and some HLL's close to the metal. For the later, you can get a list of what various constructs will look like as assembly, heuristics on what to use where, and still don't need to know compilers.
Re:Let's Build a Simple Interpreter, Part 1 (2015)
by the_duke on Monday September 12, 2016 @08:08AM
(#12478975)
But almost all software today is written in a high level language (above C).
And even in C, optimizations can change your code quite a lot.
So I do think having a basic udnerstanding of how compilers work under the hood should be required for every programmer.
As I said elswhere, every proper programmer should write at least one toy language with a compiler and / or interpreter.
I think the author really meant to say you have to understand some amount of how computers work and how compilers translate HLL's to them in order to fully understand why your HLL programs behave the way they do. That's the charitable interpretation. I'm actually writing this comment on a laptop sitting on a book that did that for me. It's called Write Great Code by Randall Hyde. Guy who made Art of Assembly Programming and HLA. It was enlightening.