News for hackers. Stuff that matters.
Re:Why I wrote a book about interpreters by Patient0 on Thursday December 01, 2016 @06:55PM (#13084755)
I would define it as: when a compiler operates on its own source code, the resultant compiled compiler executes as fast as the original. When an interpreter evaluates its own source code, the resultant interpreted interpreter is an order of magnitude slower. This definition allows for things like "just in time" compilation, and rules out silly tricks like bundling an interpreter and some source code into an executable image.
Re:Why I wrote a book about interpreters by SixSigma on Thursday December 01, 2016 @11:08PM (#13085931)
Until you get to the Forth family
Re:Why I wrote a book about interpreters by bogomipz on Friday December 02, 2016 @12:41AM (#13086310)
Why does that change with going to Forth?
Re:Why I wrote a book about interpreters by SixSigma on Friday December 02, 2016 @07:08AM (#13087932)
The speed differential. Your basically making a list of jumps into machine code and then jumping in a loop. The interpreter takes your input and turns it into a jump list which it pumps into the loop. You can reuse a jump list by defining it as a new word.
Re:Why I wrote a book about interpreters by taneq on Thursday December 01, 2016 @09:34PM (#13085492)
So compilation is idempotent? That's pithy, I like it.