C: The Complete Reference, 4th Ed.

[Helpful? Not? Please vote.] :: Mr. Hayes is undoubtedly a competent C programmer. This book isn't intended for him, nor anyone else who patently needs no introduction to the basics. For example: If you know and understand and can recognize fundamental differences between compilers (perhaps you've written a compiler or two yourself?) ... you likely don't need this book. If you know and understand different program extensions or have a nuts-n-bolts understanding of portability issues ... you likely don't need this book. If you're porting code across platforms in the first place ... I digress. I just hated to see the first review of this book rate it so poorly by being so obviously slanted or geared to the competent and experienced programmer ... Similarly, "Green Eggs and Ham" isn't really a Comparative Literature text either.This book is for new-ish programmers. I think it's specifically for undergrads who don't want to memorize the minutia of every single string function in C. Plain, vanilla C-code is all about syntax, order of operation and algorithms of the native functions. Most students understand how to solve labs on paper, but can't translate it to the infernal foreign language that is C-code. C is no mystery, and it's about exactness and handling every single possible input. It's also about reserved words, declaring and using data types and structures, and basically completing lab assignments, for the first 3 years or so. After that, C, C++, JAVA, whatever ... you know programming, and can find out what you need to complete any program in any language once you have the basics well in hand. Having taught at the University level, I find Schildt to be very good at making Sophomores out of Freshmen, and Juniors out of Sophomores. Beyond that, it's only a once-in-a-while grab to look up some small thing or another ...I used this book for undergrad and grad CS studies. It is THE preeminent reference for plain, vanilla C-language coding. It has data types, quirky ways compliers and loaders treat certain operations, and lots of "details" that you just can't and probably shouldn't remember unless you use them every day. This is the encyclopedia of C-language details, in a reference format; something lacking from K&R's books, which can have you searching and reading on a topic for some time, only to find an answer of limited utility. I do LOVE K&R's book(s), but it took a couple of years before I was fluent enough to really absorb their prose, which is no doubt, a more advanced treatment of what you can do with C. This "Schildt manual", as we called it in school, is more about HOW to do something, once you know WHAT you want to do ... This will not solve algorithm problems for you, per se, but if you're looking for the string operation that will make what your algorithm calls for easiest, they're all in here, explained with syntax and order of operations in plain English. I would hate to think what my undergrad years would have been like without this book. Worth the $$ at twice the price. (of course, people have found intermittent instances where this book was no help, or even outright wrong ... welcome to computer science and math ... ain't it grand?!?!? ... "Hilbert, meet Godel" :-)After an MS in CS, multiple applications and system level programming projects, several years in industry, and having taught introductory C-programming for 7 semesters, if I could have ONE and only ONE reference book on the C-language, this would be it. The "class time" instruction is available on any online C-coding tutorial ... the unforgiving nature of code/logic makes "correctness" imperative. Correctness is in the details. The details are in Schildt's C Reference, and they're easy to find ... thus, you can finish your lab, take a shower and make it to the party with all your friends, instead of sitting in the lab, sweating whether to use strtok() or strstr(), while your youth and "fun years in college" are ever more fleeting. Believe me, you have better things to do than try to solve a second year lab assignment using Kernighan & Ritchie ... ( K&R = "the authors", so reverently mentioned in several prior reviews, JIC that isn't common knowledge). Their books, and afrementioned reviews of this book, though correct in probably every way, are sort of like Microsoft Help Topic answers (Seebach's page contains rants from other would-be authors who seem to wish that they'd not only had the idea to write this book before Schildt, but also employed their many computer-geek buddies to help them edit it better as well. Neither happened.). To put K&R's work, as relates to the beginner, into the MS Help Page perspective:[ A helicopter was lost in the fog near SeaTac airport, radar was down, and they were flying blind. Suddenly, from the mist, appeared a large building. As people gathered by the windows to gaze at the helicopter, the passengers scrawled a sign for the onlookers, "Help! Where are we?". A few disappeared into the cubicle farm and returned with a sign reading, "You're in a helicopter!" The pilot promptly turned the chopper around, and said that's Microsoft headquarters, SeaTac is this way. "How can you know that?" they inquired. He replied, "I know it was Microsoft b/c that was a technically correct, but totally useless answer." ] That was the feeling I got early on while reading K&R. They now occupy a place of high importance in my library, but I could've held off on that purchase for some time ... just my opinion. Use Schildt until you get your parchment, then go off and organize a maverick and superior disposition of your own, like Schildt's detractors. The problems with the book are piddling compared to what it has to offer, and are unlikely to be an issue for it's intended audience.

Im really enjoying this book. It explains topics clearly and even when it uses sample programs it explains them. Im glad I bought it. But considering its a about 20 year onld book it is falling apart on me. Thats not how I got it used but the glue wouldnt hold any more. But its recommended.

Thorough, comprehensive, well-organized, and the material reaches deep, to explain how a particular feature works and in some cases, how it was developed. Anyone learning C will be better grounded with this great book within reach. Even seasoned programmers can gain from the depth.

I like the examples given in the book. Really helped me hone in on C skills.

Good book

Before buying this book, I hesitated because of the negative feedback. I own Java2 5th Ed. from Schildt, and I though a book in C would be good too.After reading the entire C fourth Edition I came with the following impression: I wish I had found this book before!.It is designed for engineer-type guys: People who wnats to read, what they need. It doesn't go for pages on silly explanations, nor it circles around topics. It doesn't even say things like: "to find out more about linked lists, go to page 310".... I hate those!.It is just that: a Complete reference. I guess people who is an absolute beginner will find it a little bit more advance (try getting one of those "Learning C in X days" books). If you know something about C, but are not an expert. This is the best reference for you when you need to quickly code something. Of course, it won't be usefull if you want to write a millions of lines program, or something extremely complex. If you need a reference for the C standard Library, this is it.Don't expect it to be an advanced book on Networking, or Real Time processing... it is just a book for Standrad C.

i did all the coding examples and read the entire book from cover to cover.on a linux laptop using GNU gcc and i learned a great deal. this book will be on my shelf for the rest of my engineering career.almost all the coding examples worked. this book is totally self contained. the best part of any software tutorial study. all you need is a C compiler and text editor.you don't need a bunch of fancy downloads.i wish all coding books were written this way.

This book is very useful to find information details about C programming language. I recommend if you want a book to get help about how to use the statements in ANSI C. There are a lot of useful code examples.