The Definitive C Book Guide and ListThis question attempts to collect a community-maintained list of quality books on the c [1] programming language, targeted at various skill levels.
C is a complex programming language that is difficult to pick up on-the-go by reading online tutorials. A comprehensive book is often the best way to learn the language, and finding a good book is the first step. It is important to avoid badly-written books, and even more importantly, books that contain serious technical errors.
Please suggest edits to the accepted answer to add quality books, with an approximate skill level and a short blurb/description about each book. (Note that the question is locked, so no new answers will be accepted. A single answer is being maintained with the list)
Feel free to debate book choices, quality, headings, summaries, skill levels, and anything else you see that is wrong. Books that are deemed satisfactory by the C community here will stick around on the list; the rest will be regularly removed.
For books that have reviews by the Association of C and C++ Users (ACCU), a link to those reviews should be added along with the book.
See also:
This question was discussed on
Meta
[6] as part of the
Deleted Questions Audit 2018
[7].
The consensus was to keep it undeleted and actively maintained.
Warning!
This is a list of random books of diverse quality. In the view of some people (with some justification), it is no longer a list of recommended books. Some of the listed books contain blatantly incorrect statements or teach wrong/harmful practices. People who are aware of such books can edit this answer to help improve it. See The C book list has gone haywire. What to do with it? [1], and also Deleted question audit 2018 [2].
The C Programming Language (2nd Edition) [3] - Brian W. Kernighan [4] and Dennis M. Ritchie [5] (1988). It is still a good, short, but complete, introduction to C ( C89 [6], not C99 [7] or later versions), written by the inventor of C. However, the language has changed and good C style has developed in the last 25 years, and there are parts of the book that show its age.
C: A Reference Manual (5th Edition) [8] - Samuel P. Harbison and Guy R. Steele (2002). An excellent reference book on C, up to and including C99. It is not a tutorial, and probably unfit for beginners. It's great if you need to write a compiler for C, as the authors had to do when they started.
C Pocket Reference (O'Reilly) [9] - Peter Prinz and Ulla Kirch-Prinz (2002).
The comp.lang.c FAQ [10] - Steve Summit. Web site with answers to many questions about C.
Various versions of the C language standards can be found here [11]. There is an online version of the draft C11 standard [12].
The new C standard - an annotated reference [13] (Free PDF) - Derek M. Jones (2009). The "new standard" referred to is the old C99 standard rather than C11.
C Programming: A Modern Approach (2nd Edition) [15] - K. N. King (2008). A good book for learning C.
Programming in C (4th Edition) [16] - Stephen Kochan (2014). A good general introduction and tutorial.
C Primer Plus (5th Edition) [17] - Stephen Prata (2004)
A Book on C [18] - Al Kelley/Ira Pohl (1998).
The C Book [19] (Free Online) - Mike Banahan, Declan Brady, and Mark Doran (1991).
C: How to Program (8th Edition) [20] - Paul Deitel and Harvey M. Deitel (2015). Lots of good tips and best practices for beginners. The index is very good and serves as a decent reference (just not fully comprehensive, and very shallow).
Head First C [21] - David Griffiths and Dawn Griffiths (2012).
Beginning C (5th Edition) [22] - Ivor Horton (2013). Very good explanation of pointers, using lots of small but complete programs.
Sams Teach Yourself C in 21 Days [23] - Bradley L. Jones and Peter Aitken (2002). Very good introductory stuff.
Modern C [25] — Jens Gustedt (2017 1st Edn; 2019 2nd Edn). Covers C in 5 levels (encounter, acquaintance, cognition, experience, ambition) from beginning C to advanced C. It covers C11 and C17, including threads and atomic access, which few other books do. Not all compilers recognize these features in all environments.
C Interfaces and Implementations [26] - David R. Hanson (1997). Provides information on how to define a boundary between an interface and implementation in C in a generic and reusable fashion. It also demonstrates this principle by applying it to the implementation of common mechanisms and data structures in C, such as lists, sets, exceptions, string manipulation, memory allocators, and more. Basically, Hanson took all the code he'd written as part of building Icon [27] and lcc [28] and pulled out the best bits in a form that other people could reuse for their own projects. It's a model of good C programming using modern design techniques (including Liskov [29]'s data abstraction), showing how to organize a big C project as a bunch of useful libraries.
The C Puzzle Book [30] - Alan R. Feuer (1998)
The Standard C Library [31] - P.J. Plauger (1992). It contains the complete source code to an implementation of the C89 standard library, along with extensive discussions about the design and why the code is designed as shown.
21st Century C: C Tips from the New School [32] - Ben Klemens (2012). In addition to the C language, the book explains gdb, valgrind, autotools, and git. The comments on style are found in the last part (Chapter 6 and beyond).
Algorithms in C [33] - Robert Sedgewick (1997). Gives you a real grasp of implementing algorithms in C. Very lucid and clear; will probably make you want to throw away all of your other algorithms books and keep this one.
Problem Solving and Program Design in C (6th Edition) [35] - Jeri R. Hanly and Elliot B. Koffman (2009).
Data Structures - An Advanced Approach Using C [36] - Jeffrey Esakov and Tom Weiss (1989).
C Unleashed [37] - Richard Heathfield, Lawrence Kirby, et al. (2000). Not ideal, but it is worth intermediate programmers practicing problems written in this book. This is a good cookbook-like approach suggested by comp.lang.c contributors.
Expert C Programming: Deep C Secrets [39] - Peter van der Linden (1994). Lots of interesting information and war stories from the Sun compiler team, but a little dated in places.
Advanced C Programming by Example [40] - John W. Perry (1998).
Advanced Programming in the UNIX Environment [41] - Richard W. Stevens and Stephen A. Rago (2013). Comprehensive description of how to use the Unix APIs from C code, but not so much about the mechanics of C coding.
Essential C
[42] (Free PDF) - Nick Parlante (2003). Note that this describes the C90 language at several points (e.g., in discussing // comments and placement of variable declarations at arbitrary points in the code), so it should be treated with some caution.
C Programming FAQs: Frequently Asked Questions [43] - Steve Summit (1995). This is the book of the web site listed earlier. It doesn't cover C99 or the later standards.
C in a Nutshell [44] - Peter Prinz and Tony Crawford (2005). Excellent book if you need a reference for C99.
C in a Nutshell (2nd Ed.) [45] - Peter Prinz and Tony Crawford (2016), a reference-style book covering C11.
Functional C [46] - Pieter Hartel and Henk Muller (1997). Teaches modern practices that are invaluable for low-level programming, with concurrency and modularity in mind.
The Practice of Programming [47] - Brian W. Kernighan and Rob Pike (1999). A very good book to accompany K&R. It uses C++ and Java too.
C Traps and Pitfalls [48] by A. Koenig (1989). Very good, but the C style pre-dates standard C, which makes it less recommendable these days.
Some have argued for the removal of 'Traps and Pitfalls' from this list because it has trapped some people into making mistakes; others continue to argue for its inclusion. Perhaps it should be regarded as an 'expert' book because it requires moderately extensive knowledge of C to understand what's changed since it was published.
MISRA-C [49] - industry standard published and maintained by the Motor Industry Software Reliability Association. Covers C89 and C99.
Although this isn't a book as such, many programmers recommend reading and implementing as much of it as possible. MISRA-C was originally intended as guidelines for safety-critical applications in particular, but it applies to any area of application where stable, bug-free C code is desired (who doesn't want fewer bugs?). MISRA-C is becoming the de facto standard in the whole embedded industry and is getting increasingly popular even in other programming branches. There are (at least) three publications of the standard (1998, 2004, and the current version from 2012). There is also a MISRA Compliance Guidelines document from 2016, and MISRA C:2012 Amendment 1 — Additional Security Guidelines for MISRA C:2012 (published in April 2016).
Note that some of the strictures in the MISRA rules are not appropriate to every context. For example, directive 4.12 states "Dynamic memory allocation shall not be used". This is appropriate in the embedded systems for which the MISRA rules are designed; it is not appropriate everywhere. (Compilers, for instance, generally use dynamic memory allocation for things like symbol tables, and to do without dynamic memory allocation would be difficult, if not preposterous.)
Archived lists of ACCU-reviewed books on Beginner's C [50] (116 titles) from 2007 and Advanced C [51] (76 titles) from 2008. Most of these don't look to be on the main site anymore, and you can't browse that by subject anyway.
There is a list of books and tutorials to be cautious about at the ISO 9899 Wiki [52], which is not itself formally associated with ISO or the C standard, but contains information about the C standard (though it hails the release of ISO 9899:2011 and does not mention the release of ISO 9899:2018).
Be wary of books written by Herbert Schildt [53]. In particular, you should stay away from C: The Complete Reference [54] (4th Edition, 2000), known in some circles as C: The Complete Nonsense.
Also do not use the book
Let Us C
[55] (16th Edition, 2017) by Yashavant Kanetkar. Many people view it as an outdated book that teaches Turbo C and has lots of obsolete, misleading and incorrect material. For example, page 137 discusses the expected output from printf("%d %d %d\n", a, ++a, a++) and does not categorize it as
undefined behaviour
[56] as it should. It also consistently promotes unportable and buggy coding practices, such as using gets, %[\n]s in scanf, storing the return value of getchar in a variable of type char or using fflush on stdin.
Learn C The Hard Way [57] (2015) by Zed Shaw. A book with mixed reviews. A critique of this book [58] by Tim Hentenaar:
To summarize my views, which are laid out below, the author presents the material in a greatly oversimplified and misleading way, the whole corpus is a bundled mess, and some of the opinions and analyses he offers are just plain wrong. I've tried to view this book through the eyes of a novice, but unfortunately I am biased by years of experience writing code in C. It's obvious to me that either the author has a flawed understanding of C, or he's deliberately oversimplifying to the point where he's actually misleading the reader (intentionally or otherwise).
"Learn C The Hard Way" is not a book that I could recommend to someone who is both learning to program and learning C. If you're already a competent programmer in some other related language, then it represents an interesting and unusual exposition on C, though I have reservations about parts of the book. Jonathan Leffler
Other contributors, not necessarily credited in the revision history, include: Alex Lockwood [60], Ben Jackson [61], Bubbles [62], claws [63], coledot [64], Dana Robinson [65], Daniel Holden [66], desbest [67], Dervin Thunk [68], dwc [69], Erci Hou [70], Garen [71], haziz [72], Johan Bezem [73], Jonathan Leffler [74], Joshua Partogi [75], Lucas [76], Lundin [77], Matt K. [78], mossplix [79], Matthieu M. [80], midor [81], Nietzche-jou [82], Norman Ramsey [83], r3st0r3 [84], ridthyself [85], Robert S. Barnes [86], smalinux [87], Steve Summit [88], Tim Ring [89], Tony Bai [90], VMAtm [91]
[1] https://meta.stackoverflow.com/questions/355588/the-c-book-list-has-gone-haywire-what-to-do-with-it