> The failure to store a represention of the parsed code was disastrous because it meant that in order to evaluate an expression or statement for a second time, the engine had to parse it a second time. Ha! They must have learned how to write an interpreter from Herbert Schildt: http://www.drdobbs.com/cpp/building-your-own-c-interpreter/1... [1989] In this piece of amusement, the Little C program is a giant null-term…
Didn't PHP also used to use the position of a fileseek as the instruction pointer?
Shell script interpreters like bash do. You can change a bash script while it's running (append, or truncate and re-write) and it'll keep going from the same offset.
But then again, shell script is in a different class of language I'd say.
#!/bin/bash
COUNTER=0
addmore() {
echo hi $COUNTER
((COUNTER++))
echo "addmore" >>$0
sleep 1
}
addmore