@cmuratori @hamishtodd1 "Coders at Work" - haven't read it.
-
-
Replying to @cmuratori
@cmuratori@hamishtodd1 "The C++ Programming Language" - the book that ruined programming for 30 years. Industry still hasn't recovered.2 replies 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@hamishtodd1 Just going to scan for any other books on this list that I liked.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@hamishtodd1 Ah, the Dragon Book! I liked that one: "Compilers: Principles, Techniques, and Tools".2 replies 0 retweets 4 likes -
Replying to @cmuratori
@cmuratori@hamishtodd1 Dragon book is nice, talks trough a lot of compiler optim. Appendix A probably most useful in every day life though.1 reply 0 retweets 0 likes -
Replying to @JasperBekkers
@JasperBekkers@hamishtodd1 There might be better books on compilers now, but I haven't read any in a long time. Back then, it was the best.3 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@JasperBekkers@hamishtodd1 The second edition modernizes it. I think it holds up.2 replies 0 retweets 0 likes -
Replying to @won3d
@won3d@cmuratori@JasperBekkers@hamishtodd1 If you use lex or yacc, you're doing it wrong. The LCC book reflects actual practice.2 replies 0 retweets 0 likes -
Replying to @nothings
@nothings@won3d@JasperBekkers@hamishtodd1 I agree at face value, but I _do_ think generation is the right approach. Just not _those_.3 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@won3d@JasperBekkers@hamishtodd1 Generation makes sense if you change your language a lot in major syntactic ways.#youshouldnt3 replies 0 retweets 1 like
@nothings @won3d @JasperBekkers @hamishtodd1 No, it's not just that.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.