What would you posit as required reading

for programming language design?

Every language is shit. There's nothing else to know. In fact, the less you know the better. By not being indoctrinated with shit, you may make something original that is not shit.

But if you want to build a compiler then the dragon book.

SICP, something to teach you CL macros.

I wouldn't require ANYTHING

All academic knowledge does is give people tunnel vision and threatens creativitiy

Real programming language designers don't have to read anything, that's where completely new ideas come from

>>1
Read TAPL and ATTPL.
>>4
Usually that's where completely old ideas come from. Because those who don't know history are bound to repeat it.

C89 Standard and K&R

>>5-san has quite a wise recommendation. There're also:

Design Concepts in Programming Languages, which is quite a great and comprehensive tome. It also uses s-expression as a notation for AST.

I heard good things about Practical Foundations for Programming Languages , but haven't had a chance to look at it yet.

And what kind of /prog/rider that doesn't read SICP. There's also Essentials of Programming Languages while we're at that.

The dragon book is overrated. One can learn substantial compilation techniques from that though. I like Lisp In Small Pieces and Modern Compiler Implementation in ML better.

>>7
Will you help me write a haskal compiler?

>>8
No, because I'm a faggot. A huge one at that. Ask Simon Peyton Jew for that shit.

>>8
Just fork GHC.

>>9
>>10
so prog is just people who list hard sounding books but don't know what's in em

>>11
Well I kinda sorta opened a couple of them once or twice. I'll get to reading them eventually, though.

>>11
Exactly. And reading them won't automatically make you a capable haskal implementor.

>>13
[citation needed]

>>14
>>9-san and >>10-kun are the citation.

>>15
That's because they READ them and not STUDIED them.