On Friday, January 13, 2017 at 12:09:52 PM UTC-5, Ian wrote:
> On Fri, Jan 13, 2017 at 3:46 AM, Steve D'Aprano
> wrote:
> >
> > http://aosabook.org/en/500L/a-python-interpreter-written-in-python.html
>
> Neat. But not really surprising IMO that it can fit into 500 lines,
> since it doesn't handle
On 13/01/2017 18:47, Ian Kelly wrote:
On Fri, Jan 13, 2017 at 11:07 AM, BartC wrote:
Even when it turns out that the actual code on github is 1000 lines rather
than 500! Maybe it grew a bit since the 500 lines was quoted.
I assume they're excluding blank lines, comments and docstrings. And I
On Fri, Jan 13, 2017 at 11:07 AM, BartC wrote:
> Even when it turns out that the actual code on github is 1000 lines rather
> than 500! Maybe it grew a bit since the 500 lines was quoted.
I assume they're excluding blank lines, comments and docstrings. And I
don't know whether the 500 lines is a
On 13/01/2017 17:08, Ian Kelly wrote:
On Fri, Jan 13, 2017 at 3:46 AM, Steve D'Aprano
wrote:
http://aosabook.org/en/500L/a-python-interpreter-written-in-python.html
Neat. But not really surprising IMO that it can fit into 500 lines,
If there are still 120 or so byte-codes, then that's just
On Fri, Jan 13, 2017 at 3:46 AM, Steve D'Aprano
wrote:
>
> http://aosabook.org/en/500L/a-python-interpreter-written-in-python.html
Neat. But not really surprising IMO that it can fit into 500 lines,
since it doesn't handle compiling Python into bytecode (which is the
hard part) and doesn't includ
