K was originally written by http://en.wikipedia.org/wiki/Arthur_Whitney_(computer_scient..., and having seen some of his C code, this looks like a very similar style. Take a look here: http://www.nsl.com/papers/origins.htm
edit: included link to a better source example
"The unusual appearance is a side effect of writing C as concisely as possible. There are great benefits to writing code in this way. Someone familiar with the style can read and comprehend the code much faster than they could with traditional code. Brevity creates a discipline that reduces bugs. Some of the benefits will not be apparent until you try it. Some of the downsides of the style are inaccessibility and a steep learning curve."
Everyone has this reaction when first exposed to this class of languages and their implementations - everyone. You're unfamiliar with the style, and you're confusing that with it being ugly/unreadable/dumb. I assure you it's anything but.
Now let's page silentbicycle and get him to explain :)
I can't speak for GP, but I promise you I've spent plenty of time reading code with single-letter identifiers. If I'm going to have to actually understand some code, I'd much prefer descriptive names.
So the single character identifiers are not intended as something application specific, or mutable values. They are like +, *, %.
That said, I still think it's better to stick to the conventions of the implementation language when writing an interpreter, rather than attempt to contort it half way to your target language. If you want a self hosted implementation, just write a compiler.
LOL. Sure, go ahead and stare at all these classes and files with single letter (and single number) names. It will make you a better PERSON.
> The C source code for this is intensely beautiful, and very concise. Go look at it!
Which links to https://github.com/kevinlawler/kona
This has to be a joke - just pick a random file and tell me what is beautiful about that. LoseThos looks saner than this code.