Skip to content

Comment on Making a Python interpreter in 1024 bytesparent

Comments

It's just a stack containing strings at the end of the day. Really not a big deal.

Care to give it a go? I'm curious to see how many bytes of the 1024 bytes your implementation would eat up.

Right, pointers to strings but yeah. Essentially the whitespace count specifies the stack depth at which a line is to be executed. A decrease in stack depth means all superior levels are terminated.

Doesn't affect function call stacks though.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.