Customer comments on this selection.
 PATHETIC
A good idea gone bad, very bad.
Teaching computer programming is a great technique, it has lots of potential for making the learning (and teaching) experience more fun pleasurable and by consequence, more effective. Unfortunately this pathetic excuse for a book does a terribly poor job in accomplishing this task.
It starts out nicely for the first easy chapters but it quickly degenerates in an unbelievably superficial mess. Snippets of code are thrown in randomly with no clue about where they fit in a real application, and the chapters and explanations become unbelievably this , short and superficial. Want an easy laugh? The chapter on templates is 3 pages long. I AM NOT KIDDING, you read well.. 3 pages long. To inheritance and polymorphism instead are devoted a full SIX pages.
They should be ashamed of publishing this bs.
As for the "game" part.. all you get are a few simple text based games like single player blackjack and a pathetic couple of simple SDL based games at the end.
Ah, I forgot, the author avoid carefully to discuss to the games code in the text, you will just have to dig in the source code CD and understand it by yourself.
Bottom line, for the potential reader AVOID LIKE PLAGUE and if you are looking for a game based intro to C++ wait for this, which has good chances of being good:
Starting Out with Games and Graphics in C++, for the publishing company shame on you for publishing this bs, and get a real editor.
 It had potential
Since I'm pretty experienced with C++, I was able to wade through the skimpy explanations of C++'s most advanced concepts without too much difficulty, but I fear that a reader new to C++ (the intended audience), will have a fair amount of difficulty.
The book starts out well -- in the beginning chapters all the code is there, it's explained, and the examples are simple enough that a beginner can easily follow. However, as the book progresses and covers more advanced topics, the explanations become increasingly brief and almost cursory! Operator overloading, one of C++'s central features, for instance,is given a few pages of explanations and code, one poor example, and then it's off to the next topic which is covered in the same amount of detail.
The main problem with this book is that it attempted to cover too much in too little space. Clearly, you're NOT going to go from a C++ neophyte to a 2D game programer in one book, in 500 or so pages. It's just impossible.
So, I give this book a 3 star rating because while it may be useful to newbies and weathered programmers alike, the later chapters will invariably prove to be extremely difficult to understand for the newbies because while code is shown and examples are shown, the *theory* and explanations behind the workings of given features are simply not present, which makes this a sub par learning tool.
 Good book bad CD
The book is well written and good examples. However the CD has many errors in the examples and is incomplete.
For Beginners ONLY
Ok this book can be a very helpful tool for a beginner, but some of the software doesn't work with vista so be careful. Also I don't like the compiler that much, but it gets the job done.
i wanted to give it a 5, but....
When I found out about this book, I was so excited! There arent many books that go over SDL, and the idea of a book that taught SDL, C++, and game coding all in one sounded like such a good idea.
If the entire book were like the first half, i'd give it a 4.5. With full code listings, and great explanations, I feel like someone could really learn alot from this bit of the book. The only problems I had with the first half is, the author starts the reader out fast, and explanes as you go, wich is hard for someoen who is totally new. Overwhelming the n00b is not a good idea if you want him to continue. The second thing I kindof thought was silly was, static_cast. Using the code "double quotient = 5 / 4;" the author says you cant get a floating point result without either typing it out like "double quotient = (5 + 0.0) / 4;" or "double quotient = static_cast(5) / 4;". I say, how about trying this "double quotient = 5.0 / 4.0;". And to quote the author
"the division (5 + 0.0) / 4 will be a floating point-operation. However, this is an ugly hack and introduces an unnecessary addition."
ROFLOL
After that sillyness, I was tempted to not read the rest of the book. This all happens on pg 61 btw.
Anyways, back on track. The author does a good job through the rest of the first half of the book, ignoring that silly static_cast. Then for some reason, it all falls apart. The BlackJack game is where I really started feeling frustrated. His explanations were still on key, but something was missing. THE CODE! He stops listing the complete code in the book, and instead has you refer to the cd. The author also does this in several cases when introducing new threory's, he says something like "the new code can be applyed to the listing in chap 1, or you can look at the cd". In my opinion, this is terrible for several reasons. Let me just list a few.
1.I bought the book used on amazon, and it didnt have the cd.
2.Used book w/out cd, and I have no net access.
3.I rented the book from the library, and the cd looks like a dog frisbie.
4.My cdrom drive is broken/I have none.
Ok, ok, i'll stop at that. As none of these reasons effect me, the reason I'm annoyed by it is, if you put the code in the book, and not on a cd, it encourages the reader to actually type it in, and see it all. If you put it all on cd, the user will be tempted to copy/paste, and will not learn as much as they could have typing in all the code. Afterall, programming is typing, and if your not willing to type out whats in the book, you might as well quit right now.
I've read tons of coding books, and I've been coding for about 2 years now. Some of the books I've read were really good, and some of them were really bad. Unfortunately, the things that make a book of this nature "great" seem to be missing after the first half. In the first half of the book, the author has shown that he is capable of doing a good job, perhaps a second edition is in order?
|
