I’ve read the whole Dragon Book recently (just for fun, I’m not really planning to implement an actual compiler), and I was left with this big question dangling in my head.
What is different between implementing a compiler and an interpreter?
To me a compiler is made up of:
- Lexer
- Parser (which builds the syntax tree)
- Generate Intermediate code (like 3 address code)
- Do all these crazy things to optimize if you want 🙂
- Generate ‘assembly’ or ‘native code’ from the 3 address code.
Now, obviously, the interpreter also has the same lexer and parser as the compiler.
But what does it do after that?
-
Does it ‘read’ the syntax tree and execute it directly? (kind of like having an instruction pointer pointing to the current node in the tree, and the execution is one big tree traversal plus the memory management for the call stack) (and if so, how does it do it? I’m hoping the execution is better than a huge switch statement that checks what type of node it is)
-
Does it generate 3 address code and interpret that? (if so, how does it do it? Again, I’m looking for something more elegant than a mile long switch statement)
- Does it generate real native code, load it into memory, and make it run? (at which point I’m guessing it’s not an interpreter anymore, but more like a JIT compiler)
Also, at which point does the concept of ‘virtual machine’ cut in? What do you use a virtual machine for in a language? (to be clear about my level of ignorance, to me a virtual machine is VMWare, I have no idea how the concept of VM applies to programming languages / executing programs).
As you can see, my question is quite broad. I’m mostly looking for not only which method is used but mostly to first understand the big concepts, and then get into how it works in detail. I want the ugly, raw details. Obviously, this is more a quest for references to things to read rather than expecting you to answer all these details in here.
Thanks!
Daniel
EDIT: Thank you for your answers so far. I realized my title was misleading though. I understand the ‘functional’ difference between a compiler and an interpreter.
What i’m looking for is the difference as to how you implement an interpreter, vs a compiler.
I understand now how a compiler is implemented, the question is how an interpreter differs from that.
For example: VB6 is clearly both a compiler and an interpreter. I understand now the compiler part. However, I can not grasp how, when running inside the IDE, it could let me stop the program at any arbitrary point, change the code, and resume execution with the new code. That’s just one tiny example, it’s not the answer i’m looking for. What i’m trying to understand, as I explain below, is what happens after I have a parse tree. A compiler will generate new code from it in the ‘target’ language. What does an interpreter do?
Thank you for your help!
short answer:
there is a great deal of leeway in how either are implemented. It is possible for an interpreter to generate native machine code and then execute that, while a compiler for a virtual machine may generate p-code instead of machine code. Threaded interpreted languages like Forth look up keywords in a dictionary and execute their associated native-code function immediately.
compilers can generally optimize better because they have more time to study the code and produce a file for later execution; interpreters have less time to optimize because they tend to execute the code ‘as is’ upon first sight
an interpreter that optimized in the background, learning better ways to execute the code is also possible
summary: the difference really comes down to ‘prepare the code for later execution’ or ‘execute the code right now’