- Amazon Student members save an additional 10% on Textbooks with promo code TEXTBOOK10. Enter code TEXTBOOK10 at checkout. Here's how (restrictions apply)
C How to Program (5th Edition) Paperback – Aug 25 2006
Special Offers and Product Promotions
Customers Who Bought This Item Also Bought
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
To get the free app, enter your e-mail address or mobile phone number.
About the Author
Dr. Harvey Deitel is one of the world's leading computer science instructors and seminar presenters, and author of more than a dozen books. He worked on the pioneering operating system teams in industry and academia that developed many of the techniques at the heart of operating systems like UNIX®, Windows NT™ and OS/2™.Paul Deitel has taught Visual Basic, Java, C and C++ at numerous hardware and software companies, including Sun Microsystems, Digital Equipment Corporation, IBM, Open Environment Corporation, Adra Systems, and Cambridge Technology Partners, and is himself an expert developer.
The Deitels are principals of Deitel & Associates, Inc., an international training organization specializing in Visual Basic, Java, C and C++, and object technologies.
Most Helpful Customer Reviews on Amazon.com (beta)
I just finished a course on C, and the instructor opted to use this book. My first impression of the book was that it's way too expensive and it's way too big for a friendly introduction to C. From the size alone and the ten different subheadings, I had a feeling this was going to be a prime example of what I call Textbook Syndrome, and indeed it is now my main example of this phenomenon.
Textbook Syndrome is an unfortunate disease afflicting most authors who write books used for introductory freshman and sophomore college courses. In short, Textbook Syndrome causes an author to write for the people teaching from the book, not the people learning from it. It is believed that Textbook Syndrome is contagious and is spread via the propagation of poorly understood flimsy green entities; the development of a cure and preventative measure is an open question in science today.
For diagnostic purposes, here are a few common symptoms of Textbook Syndrome, all exhibited keenly by the present book:
(i) The book includes about ten times as much material as could reasonably be covered in a one-semester course. This is done so that (a) the book is bigger and therefore both looks more substantive and costs more; (b) it can be used for any course on any topic remotely related to the book's title; (c) it can be used for both introductory courses and advanced courses. The math is simple: (a) + (b) + (c) = a blatant attempt to maximize profit, nothing else.
For the student, it means he must carry around an ancient thousand-page tome, the majority of which will never be useful to him. For the teacher, it means he must (perhaps ironically) put more effort into actually providing the course with a coherent structure, as the book itself, so overburdened with unnecessary material, could never hope to achieve any sort of coherence.
This is a book on C, as the title suggests. It's also a book on game programming. It's also a book on C++ (count them: ten chapters). I wonder if they will add another ten chapters on Java in the next edition.
(ii) Exercises range from fill-in-the-blank questions about what preprocessor directive to use to include one file in another (I am not kidding) to a team-based, multi-month extravaganza to develop a compiler from scratch. Books written by authors having Textbook Syndrome often exhibit what I will call the intermediate value property: given two extremes possessed by the book, the book will also possess everything in between.
The present book indeed has the intermediate value property. Every imaginable exercise in between the two above extremes is present at the end of each chapter. Presumably this is so the book is useable at the same time by everybody on the planet Earth from Ph.D. physicists and mathematicians at NASA to novice junior high students who aren't up to speed on the concept of "computer." (For the latter group, worry not: the first chapter will help clarify the purpose of these auspicious contraptions.)
(iii) Very important pieces of information are inexplicably missing. The standard function gets() is mentioned, but it is not mentioned that this function should almost never be used. Even the man page for gets explicitly states it should not be used, but this thousand-page tome can't even provide this nugget of actually useful information.
(iv) The book includes vocabulary lists (just words, no definitions) at the end of every chapter since, you know, memorizing vocab words is useful while one learns to program. (Technically, this is a special case of the intermediate value property discussed in point (ii), but the vocab lists are so stupid I wanted to give them the emphasis that comes with having their own point.)
I could go on, but I will conclude this review with a description of who I think must be the quintessential intended user of this book. You should buy this book if you have money to blow, you believe that copying and pasting bits of text from a dozen other books is the height of authorship, you want to support the financial decline of many poor and starving computer science students who are forced to purchase books like this, you believe vocab lists are relevant to computer science (and therefore you have absolutely no computer science education whatsoever), you don't know the meaning of the word "focus", and you have long lost any respect for titles (who are these titles to dictate the contents of books anyway?).
edition of Deitel's "C++: How to program". I now regret that decision.
The two biggest flaws of this book are;
1)The lack of integration of the c99 standard into the text and examples. There is a (brief) chapter bolted on as kind of an after thought. Given that this standard had been out for at least 5 years since this edition was published it seems a bit lazy to not include more references to modern C earlier in the book.
2)The rather large focus on C++. 10 out of the 27 chapters deal with C++. If I had wanted a book on C++ I would have brought one, if fact, I did. This space could have been used on so many other useful things, like, how to produce larger C programs, or a non-windows IDE option for compiling.
On the plus side, there are plenty of chapter review questions, and exercises and pretty in-depth coverage of the c89 standard.
My advice is, if you want to know a bit about C as a stepping stone to C++, get the Deitel C++ book C++ How to Program (6th Edition) as it covers this information. If you want to do plenty of homework on C89, save yourself a lot of money and buy a second hand copy of an older edition.".C How to Program (3rd Edition) If you want to learn modern C and not C++, get another book.C Primer Plus (5th Edition)
1. Game Programming
2. Eliminated the Java stuff
3. More on C99
Wish it was a strictly C book (no C++ sections in it)
The comprehensive exercises provided at the end of each chapter helps the learner practice what he has learnt and it also makes this text ideal for college courses.
The fact I liked mostly about the book is its highly descriptive nature. They have missed nothing. (They ought not! since the book has more than 1000 pages.)
Look for similar items by category
- Books > Computers & Technology > Microsoft > Development > C & C++ Windows Programming
- Books > Computers & Technology > Programming > C
- Books > Computers & Technology > Programming > Languages & Tools
- Books > Computers & Technology > Software
- Books > Qualifying Textbooks - Fall 2007 > Computers & Internet
- Books > Textbooks > Computer Science & Information Systems > Programming Languages