4 ms·
The problem I always have with this kind of article is that even though they, like this one, are often well written and clear they skip all discussion of the ch
by kwhitefoot 10y ago
The problem I always have with this kind of article is that even though they, like this one, are often well written and clear they skip all discussion of the choice of language to implement as though this is somehow completely irrelevant to the task of creating an interpreter.
But it is not. An interpreter for a curly bracket language or Algol descendant (Algol, C, C++. C#, VB.Net, Pascal) looks quite different from one for a stack based language (the canonical one being Forth I suppose) and different again from on that uses S-expressions (Lisp, Scheme, etc.), and so on.
A simple interpreter for a stack based language can be a lot shorter than one for a block structured language