Thank you for this fantastic reply Sam! I now think I had a very naive model of "interpreter" when I asked the question. My CS degree from the nowhere university has it that language interpreters walk the tree and you know "execute" be it in the host language or generating native code. I feel a bit stupid now. Technically you're absolutely right - there is an interpreter for the bytecode (or whatever), so duh. But there are also a bunch of compilation steps in between. I am now completely lost as to what constitutes a compiler and what makes an interpreter. I always thought of interpreters as something I encountered in PLAI. I remember reading some old paper abound "fast interpreters" and all of them implemented a virtual machine they "compiled" to and I was lost then - how's that not a compiler - as I am lost now.
-- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/b183ae65-524d-4e70-9bee-ce0531bf21feo%40googlegroups.com.
