Rating: 
Summary: Not for beginners
Review: It's unfortunate that this book got so many bad reviews. I have an earlier version (copyright 1993). This book is not for beginners and it should not be used as an itroductory text for C++ in college or by self-teachers. This book is for computer scientists who have a working knowledge of how a binary program is implemented and executed at the machine level. Assuming this knowledge, it goes on to explain the semantics of scoping, parameter passing, casting conversions, and creation and deletion of objects - as well as other important concepts. And, furthermore, it explains these semantics tersely. It wouldn't hurt to have had an introductory course in C++ before you buy this book. This book concisely explains things like when and why you should or shouldn't create a copy constructor; whether the default constructor or one of the overloaded constructors is called and why; when and why you should or shouldn't declare a member function const; when and why you need to create cast operators in your class and when and why they are called. For example, there are many instances when one of YOUR constructors or cast operators is implicitly called by the compiler generated code and not by YOUR code. If you don't know when these instances occur then you simply do not understand how your own code works. Whether you learn these concepts from this book or another is irrelevant - if you don't understand them you'll never be able to implement a non trivial abstract data type that others would be willing to pay money for.
Rating: 
Summary: Not flashy, but has the essentials
Review: This book assumes prior knowledge of programming; preferably in C or some C++. Not for beginners. Has the merit of not being too verbose. It deals mainly with the syntax of C++. And, yes, while it certainly covers OOP, this may be why some other reviewers say it is not a good OOP book. The thing is, if you have start explaining the language at the lowest level, syntax, then this necessarily takes up space in the book. What some may notice is the lack of diagrams, whether UML or flowcharts or whatever. There is relatively little coverage of higher level design, from an OOP standpoint or any other, for that matter. Plus, unlike some more recent programming books, which use multicolours on the text pages to draw the reader's attention, this is very much a traditional text, in plain black and white. Nothing wrong with that, but some of you expecting a more "popular" style should look elsewhere. But if you knuckle down and read this text, you can benefit.
Rating: 
Summary: Look elsewhere
Review: This book is one of the most poorly contstructed quasi-textbooks I have seen. I had to buy it for a C++ class, and have found the following:
1) The text does a bad job of explaining topics fully.
2) The end-of-chapter questions are written so poorly that they are not able to be done without finding out their hidden meaning.
3) The appendices are incomplete. If you need a real C++ or C book see Deitel and Deitel and leave this waste of trees alone. I find myself constantly having to refer to "C++ How To Program" to figure out my programming projects, and it comes through every time.
Rating:
Summary: Look elsewhere
Review: This book is one of the most poorly contstructed quasi-textbooks I have seen. I had to buy it for a C++ class, and have found the following:
1) The text does a bad job of explaining topics fully.
2) The end-of-chapter questions are written so poorly that they are not able to be done without finding out their hidden meaning.
3) The appendices are incomplete. If you need a real C++ or C book see Deitel and Deitel and leave this waste of trees alone. I find myself constantly having to refer to "C++ How To Program" to figure out my programming projects, and it comes through every time.
Rating:
Summary: One of the worst books on the subject
Review: This book is probably the worst book to learn C++. The author mistakenly assumes that the reader is a highly advanced computer scientist, thereby leaving novice programmers totally confused. Techinal terms are bandied about with inadequate definition. The author finds it more important to throw out concept after concept rather than attempting to explain each one clearly and thoroughly. As such the entire book reads more like a research paper than something one would expect to learn from. The chapters are poorly organized. Examples start out attempting to showcase a concept but almost always end up including something that hasn't been covered before. It is often necessary to refer to another book on the subject just to understand something in Pohl's book -- which begs the question, why use Pohl's book in the first place? There are definitely much better books on the subject.
Rating:
Summary: Great book! Discard reviews saying it does not cover OOP
Review: This is a great book, however this is not for beginners. I only started reading this after 2 years of intensive study of the language. I learned the most about OOP from this book. The person who wrote that this is not about OOP only based on the chapter titles obviously did not read the book and has no clue what OOP programming is about, otherwise he/she would have realized that each chapter covers a different aspect of OOP.
Rating:
Summary: One of the best
Review: This is one of the best books I have ever read. It is not for beginners but it is a goody for people need to improve understanding and feeling for C++ programming.
Rating:
Summary: please donot waste time on it. just throw it away
Review: this is the worst book which I had read. Boring!
Rating:
Summary: shouldn't be recommanded
Review: This is the worst textbook I've read, the contents are not well orginazed, and the examples are repeated more than once, ome of the variables are come from nowhere, I saw most of these example and almost the same words on somewhere else other than this book, those are published earlier,this book is not worth to buy at all.
Rating:
Summary: Doesn't Stack Up
Review: This text is definately not for new programmers, but even seasoned programmers will be lost in space. The author takes a very simple approach to some topics, and then quickly goes into examples that do not make sense and have no meaningful explanation (if any explanation at all). I have read texts on Object Oriented programming and C++, and this one fails to unite the two in any meaningful way. There is a healthy sampling of exercises at the end of each chapter, but I could not find the solutions anywhere online. I emailed the author and asked where I could get the solutions, and he graciously replied. Unfortunately, he sent only a short message that said there were no solutions. Did he mean the exercises are unsolvable or that the published solutions are not available? This response sums up the content of this book. I suggest looking elsewhere.
| 
