A Python Interpreter Written in Python (2016)
aosabook.org
A Python Interpreter Written in Python (2016)
1–10 of 42 posts
Re: A Python Interpreter Written in Python (2016)
#2Re: A Python Interpreter Written in Python (2016)
#3 Last-Modified: Sat, 09 Jul 2016 12:15:59 GMTRe: A Python Interpreter Written in Python (2016)
#4But can the interpreter interpret itself?
Re: A Python Interpreter Written in Python (2016)
#5But can the interpreter interpret itself?
Re: A Python Interpreter Written in Python (2016)
#6(2016), according to the HTTP headers: Last-Modified: Sat, 09 Jul 2016 12:15:59 GMT
Re: A Python Interpreter Written in Python (2016)
#7(2016), according to the HTTP headers: Last-Modified: Sat, 09 Jul 2016 12:15:59 GMT
Last-Modified: Mon, 20 Apr 3018 13:37:00 GMT
Then we will see what people say when my stuff is posted :^)Then again my stuff probably wouldn’t get much attention to begin with.
But if it did...
People would have to admit that they are all living in the present whereas I was living in the future.
Re: A Python Interpreter Written in Python (2016)
#8But can the interpreter interpret itself?
It isn't a LISP :P
Re: A Python Interpreter Written in Python (2016)
#9Re: A Python Interpreter Written in Python (2016)
#10(Technically the base interpreter is a subset/restricted version of Python however). The reason this is done (my understanding), is that a the python source code for the base interpreter can be fed into a JIT generator, which produces a Python interpreter that can perform JIT optimizations.