Rating: 
Summary: Beginners, don't waste your money on this
Review: The author tried somewhat to explain as much detailed possible from chapters 1 through 9 but then starts skipping explanation and by the time you get to chapter 13, you wonder what has been going on. Especially on chapter 16, there is little to no explanation of friend functions and classes. This book is good for intermediate programmers, not for beginners. If you are the beginnner, buy something else.
Rating:
Summary: THis book is only nice at the beginning.
Review: Don't waste your money on this ... book. It may make sense from first 8 chapters and then the author brings examples that are totally new with very little or no explanation. You will be disappointed by the time you reach chapter 12. This book doesn't teach you C++, only shows you what C++ can do.
Rating:
Summary: Bad Examples, Bad Explinations, Bad, Bad, Bad
Review: I have been programming since I was 12 years old, for about 21 years up to now. I have been a professional programmer for over 12 years and have taught myself just about every language out there. I had always avoided C++ because I could always write something quicker or simpler in Java, DBase, Pascal, VB, SQL, etc. Finally I forced myself to take the plunge and give ol' C++ a try.Having a great deal of experience in Java, Javascript, and Pascal I already knew the basic syntax of C type languages. And of course I know the ins and outs of programming very well, otherwise my check would not say "Systems Analyst" it would say "Burger Flipper." This made the first 8 days of the book really boring. I found myself flipping through the pages to get to something I didn't already know. I finished those "days" in about 3 hours. Don't get me wrong, I wasn't upset the author took an enormous amount of time on those simple concepts, in fact I was glad that he had. I figured that meant he would do an equally in-depth job on the more complex problems. Boy was I ever wrong. Right after he leaves off with the simple stuff and starts getting in to the interesting concepts, he stops explaining things and starts using concepts he hasn't even brought up yet! Here I am looking at the code and trying to figure out what this new thing is instead of concentrating on the lesson at hand. I thought it might be that I had skimmed over the first few days so I went back and spent more time on them, 2 days to be exact. That wasn't it. The author seems to have been in a rush to finish the book after the first seven days. I would not recommend this book to my worst enemy. Don't be fooled by all the good reviews. Take a look at the authors of those reviews, see how many only have one review? Looks like the author is upping his stats by writing his own reviews.
Rating:
Summary: Bogus Reviews
Review: ...This is a horrible book with little if any value. I am a professional programmer and a writer, take my word for it, this book is not worth the pulp it's printed on.
Rating: 
Summary: Quick way to learn C++ only if you have prog. experienc
Review: If you are an intermediate programmer who wants to learn the syntax of C++, then this is a good book to learn it on the fly. It would be very very helpful if you knew some of the concepts of programming, compiling, etc...
Rating: 
Summary: Teach Yourself How NOT to use C++
Review: I should have known I was in for a bad time when the very first "Hello World" program wouldn't compile as it was taken from the book. Overall the author is inconsistent, contradictory, and confuses the issues by purposely showing you examples of how not to do things instead of how to do them. The author makes the argument the you should be consistent in your coding and then immediately contradicts himself by writing code differently on many examples. For instance he says, "Most programmers us a 'p' prefix before a pointer variable." And shows several examples using the 'p' prefix. Then in the next section he goes on merrily ignoring this very important indicator. The befuddled neophyte is left scratching their head wondering why the pointer variable in an example doesn't have a 'p' as a prefix, or if it is a pointer at all. Also he seems to randomly use or not use variable names in function prototypes. Is there a reason for this? We'll never know, the author doesn't deem such an important issue worth mentioning. He just starts doing it when the occasion suits him. After wasted hours pouring over pointlessly in depth explanations of such mundane topics as "What a variable is," I was shocked at the lighting fast and totally unexplained section on operator overloading. While the author takes a great deal of time explaining a simple concept like what a stack of memory is, even going to the trouble to show a picture of a stack of dishes, he doesn't even bother to mention how the compiler knows if an overloaded operator is a prefix or postfix overload! Instead, you are left looking at mystery-meat code, wonder what that integer does and where the overloaded operator gets it from. A simple, "When overloading an operator use no parameters for a prefix overload, and use an integer parameter for a postfix overload. The parameter is not used but is required because overloading a function or operator requires each version of the overload to have different parameters." I would not recommend this book to anyone that has even a little bit of programming experience because you will be so bored with the simple concepts that you will be skimming chapters to get to the good stuff and miss the haphazardly placed important information. I would defiantly not recommend this book for someone with no programming experience because you will be left in the dust after the seventh day.
Rating:
Summary: Great book for learning C++ from scratch
Review: I have always wanted to learn C++, but never had the time. I was browsing through the bookstore and came across "Teach youself C++ in 21 days." I figured "yeah, sure, I'll be programming in 21 days. Sure...... Well, after I did the 21 day tutorial I have a real grasp of C++. I can program out simple codes, along with more complex ones. The only reason I didn't give it 5 stars is because it doesn't go into real depth, but because of that, it's a great stepping stone for more advanced books and programs.
Rating: 
Summary: Excellent intermeadiate book
Review: I have several C++ books at work but this is the one that I refer to most often, and it's the one my co-workers are most likely to borrow. I had already learned C++ before I read Jesse's book, so I don't know if it's that good for a complete beginner -- but it is excellent for the intermeadiate student who really wants to learn how inheritance and polymorphism work, as well as some other fairly advanced concepts such as function pointers.
Rating:
Summary: Really good book!
Review: I found this book to be extremely useful in beginning programming with C++. I tried a lot of other "tutorials" only to find that they were terribly confusing and only showed code, not how it worked.
Rating:
Summary: How does he do it over and over and over again?
Review: Jesse Liberty has done in again! managed to cover every penny detail of C++ with lots of examples! And the best point is: they have hundreds of errors in them, even after three additions before! So you have to learn it yourself! That's what they mean by "teach yourself"! You don't expect him to teach you, do you?! if you want someone to teach you, get a different book!
| 
