In theory, it might be nice to do something along the lines of Ruby, Python or Javascript, but those languages are, I think, too far removed from the CPU opcodes to get the same effect. Meta-circular interpreters, like in Lisp etc., are cute and are good for explaining the fundamental semantics of the language, but there's still an awful lot of magic baked in, in the same way that a C compiler written in C can embed the meaning of '\n' as a '\n' literal constant in the source itself. Of course, that magic may be subverted, most famously in the trusting trust essay:
I have a feeling that most people with the will to read a tutorial on compilers, and actually make it through the first chapter, are smart enough and work hard enough to figure it out.
[1] In case anyone's interested: http://github.com/samsonjs/compiler instead of emitting assembly instructions it emits x86 machine code directly.
Interesting how something from 1988 can still be applicable today, even if pascal is 'mostly dead' the principles are valid.
It would be neat if someone took this as a base and used it to implement - and document - a language that people are more familiar with today.
If not for Borland Pascal would have died out long ago, but even today a fairly large number of people still hold on to the modern incarnation of it.