4 ms·
I program primarily in C and believe I know all there is to know about it. But I have never read K&R. A few weeks back, I started reading it, got bored and gave
by justanotheratom 16y ago
I program primarily in C and believe I know all there is to know about it. But I have never read K&R. A few weeks back, I started reading it, got bored and gave up. But I keep running into people who swear by K&R. Do you guys think it is worth a read after the fact?
- tomlogic 16y agoMaybe not. If you're at that level, consider reading "The Standard C Library" by Plauger. I used it as a reference for updating a non-compliant library to be mostly compliant. I gained a better understanding of why the standard C library is the way it is, and learned how to implement all of it.
- spc476 16y agoI've been programming in C since 1990, and I still use K&R, although it's mostly Appendix B (the Standard Library) at this point (I find it easier to read than the man pages). The only other C book I have (and consider worthwhile) is Plauger's _The Standard C Library_, not only for his implementation but for the history behind the Standard Library.
- follower 16y agoI've never understood the love people seem to have for K&R--especially as a beginner text. In the end I put it down to learning approach differences. A decade ago I thought the book "C Programming : A Modern Approach" by K.N. King was a good starter text--I don't know if there's a better recommendation that's more recent. In terms of after the fact reading, if you like the terse style of K&R you might pick up something but if you got bored I suspect that means you don't like the style. I suspect the time might be better spent reading some code instead.