top | item 40951194

(no title)

chris37879 | 1 year ago

I feel like this is a book most programmers should work through at some point or another. Doing so made me really appreciate just what's going on inside a compiler / language toolkit. It's also one of the most well written technical guides I've ever followed, it really helped me internalize the concepts, and they are useful all over the place, not just in compilers.

discuss

order

sva_|1 year ago

This comment sold me. Gonna keep this as an inactive tab for the next couple months.

BoiledCabbage|1 year ago

Just to be safe, make sure to also copy the url into a note app, or some other location where you'll never look at it again.

fuzztester|1 year ago

Redirect it to /dev/null, that way you'll never see it again, so won't feel guilty:

$ cat this >/dev/null

Bonus points for redirecting standard error to standard output:

$ cat this >/dev/null 2>&1

Now no one will hear the screams ...

phyrex|1 year ago

Why not buy an copy and put it on your to-read shelf for the next couple of months?

fuzztester|1 year ago

>really helped me internalize the concepts, and they are useful all over the place, not just in compilers.

Which are some of those places? Parsing data formats could be one, I guess.

turndown|1 year ago

IMO compilers make you a lot more mature in recursive algorithms and trees, and then after that much more conscious about what exactly the code you write resolves to in terms of that languages semantics. Learning how closures work(variable capture and having to traverse the scope stack to find bound variables) is also a positive.