Object-Oriented Programming Using C++ (The Benjamin/Cummings series in object-oriented software engineering)

Rating:
Summary: an odd approach to a complex topic
Review: I bought this book after reading Pohl's "C++ for C programmers" and found it to simply be a beefed up version of the same book without the part about the C kernel language. Pohl has an odd way of approaching the complex topic of C++ and writes in a manner which is at the opposite end of the spectrum from the "C++ for Dummies" type books (I read & liked C++ for dummies). I was forced to buy and read other books on the same subject in order to fully appreciate the language, but this book is not without its merits.

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: 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.