3 ms·
> [...] should be mandatory reading for anyone getting started with compilers. Well, only for those folks who you taint with C before you let them loose on com
by eru 2y ago
> [...] should be mandatory reading for anyone getting started with compilers.
Well, only for those folks who you taint with C before you let them loose on compilers. If you follow something like https://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_Hours https://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_... as your introduction, I doubt you would benefit from worrying about pitfalls of C.
- pizlonator 2y agoBut then you’d want your compiler to infer loops from tail recursion and then you’d have all of the same problems as this paper cites. The paper’s title is misleading in that way. It’s describing problems with loops, not problems with C loops.
- eru 2y agoThat's a good point. I guess I would say the article (or something like the article) is good for someone just a bit beyond 'getting started with compilers', but that's probably just a matter of exactly where you draw the line between beginner topics and slightly more advanced ones.