Getting Started With Reema Thareja Programming In C
I picked up Reema Thareja Programming In C back when I was teaching a first-year university course and needed a text that wasn't completely dry but also didn't waste pages on fluff. The book is structured around worked examples, which is its main strength. Each chapter builds from basic syntax through pointers, file handling, and into some advanced topics. The examples are short and follow a pattern you can actually study rather than just read past. The textbook is available through most major online retailers and campus bookstores. Oxford University Press lists it on their site. If you're looking for supplementary material, the companion website used to host solutions and PowerPoint slides, though access sometimes requires an instructor verification code. There are also user-uploaded solution PDFs circulating on various academic document-sharing sites. I found the code examples on the publisher's page most reliable since community uploads sometimes have typos that break compilation. The book itself costs around forty to fifty dollars for the paperback edition depending on where you buy it. The e-book version is slightly cheaper. If you're a student on a budget, checking whether your university library has a copy or two on reserve is worth doing first.
How the Book Actually Works in Practice
Most C programming textbooks assume you already understand why you're learning something before they explain how. Thareja's approach is different. She shows the code first, usually a complete runnable program, then breaks down what each part does. This works well for visual learners but it means you should type out every example yourself instead of just reading them. I've seen too many students flip through the chapters thinking they've absorbed the material when they've barely done anything hands-on. The chapter on pointers is where this book earns its reputation. The explanation of pointer arithmetic and array-pointer relationships is clearer than most competitors. She uses diagrams alongside the code, which helps when you're trying to picture what's happening in memory. The section on function pointers is decent but not deep. If you need advanced coverage on that topic, you'll still need a reference like K&R or a dedicated systems programming book. One thing the book doesn't handle well is modern C standards. The examples lean toward C90 and C99. If you're working on a project that requires C11 features like _Generic, static assertions, or proper threading support, this book won't cover it. That's not really a flaw in the book itself since it's designed for introductory courses, but it's something to keep in mind if your curriculum has moved forward.
A Problem I Ran Into and How I Fixed It
During a debugging exercise in Chapter 8 on file handling, I hit a case where a student's code using fgets was reading one extra character from a line that should have been empty. The book explains fgets behavior but doesn't explicitly call out the newline retention issue in a way that addresses edge cases with mixed fgets and scanf calls. The workaround was straightforward: add a character consumption loop after any scanf that leaves data in the buffer, or switch entirely to fgets for all input and use sscanf for parsing. I made the students write a small function called consume_buffer that reads characters until it hits a newline, and that solved about eighty percent of the file-I/O related bugs we were seeing. Another thing worth noting is the book's treatment of dynamic memory allocation. The examples work fine for simple cases, but when students try to free memory that's been passed through multiple function calls, they run into double-free issues that the text glosses over. I recommend pairing the relevant chapters with a valgrind walkthrough so people actually see what happens when pointers go wrong.
Get the Full Details
What This Book Is Good For and Where It Falls Short
The book is solid for self-study at an introductory level. The problem sets at the end of each chapter range from straightforward to moderately challenging. The answers to selected problems are available in an instructor manual, which means if you're learning on your own, some exercises don't have verified solutions to check against. You'll need to rely on online forums or compiler output to validate your work on the unanswered ones. The indexing is adequate but not great. Looking up a specific concept like "string reversal without strlen" might take a few pages of flipping. The table of contents is more useful for navigation than the index. If you're taking a formal course that adopts this text, it covers roughly what you need in the first semester. After that, you'll want something more rigorous. I usually recommend combining it with online resources like the GNU C documentation for when the book's explanations hit their limits. The book gets you to a functional level of C competence. Going beyond that requires supplemental material and actual project work.
The code examples are written in standard C with no platform-specific extensions, which is good. Everything compiles cleanly on GCC, Clang, and MSVC with default settings. I haven't run into any examples that break on different compilers, which is more than I can say for some other textbooks in this space.
