11–14 of 14 posts
Earlier quoted context omitted.
You can use this tutorial for the first step if you want to do it: Write Yourself a Scheme in 48 Hours by Jonathan Tang. http://jonathan.tang.name/files/scheme_in_48/tutorial/overvi...
It would be interesting to see how many languages you could nest before the interpreter becomes too slow to be of use.
A compiler, if asked to "execute" itself a million times will generate code that is still reasonably fast.
An interpreter, if asked to "execute" itself a million times, will generate code that is a million times slower.
https://bitbucket.org/quiark/hsc
The whole purpose of that mental gymnastics was to learn x86 assembly while practicing my Haskell ;)
Earlier quoted context omitted.
It would be interesting to see how many languages you could nest before the interpreter becomes too slow to be of use.
I've always thought that this would be a better definition of what a "compiler" is vs what an "interpreter" is: A compiler, if asked to "execute" itself a million times will generate code that is still reasonably fast. An interpreter, if asked to "execute" itself a million times, will generate code that is a million times slower.