I learned C++ from Stroustrup''s book, though I already knew java. Took a week, I''m not boasting either (I mean why would an anon boast right?). So get Stroustrup''s book and just read it cover to cover. Even if it turns out that you can''t learn from it just put it aside because you do need to read the entire thing once. Buying a book on VC++ is not at all the same as buying a book on C++. They are entirely different. VC++ is a program, C++ is a language. A book on VC++ would be nice too if you have the money, but I am doing just fine without one.

quote: I''m reading a book called "learn C++ in 21 days" (it''s online readable from: "http://members.tripod.com/~firstpod/cpp21/" ).
but I''m using visual c++ 6.0 and when I type the code standing in the book. Their are almost every rime errors. Can someone please tell me what I do wrong??

You''re most likely just not typing the code in correctly.

Good DirectX books: Tricks if the Windows Game Programming Gurus
The Zen of Direct3D game programming

------------------------------
BASIC programmers don''t die, they just GOSUB and don''t return.

Buy the 2nd edition of TOTWGPG that just came out. Actually, it came out like 3 weeks ago but I''m still hunting for it in my local B&N. I think it''s updated to cover DX8, but don''t take my word for it.

I must agree with most of the other post about a programming book. Totwgpg will give you a solid idea of what it takes to program a game. Even though some of it is out of date, the stuff everyone is doing now will be out of date in a year or two. Learing new things is part of programming. And learning how it was done in the last couple of years is good if you want to understand older code.

As for learning the c++ stuff myself, I am self taught, but now going through college. The book we use in class, "C++ programming today by Barbra Johnston" is very good, because it presents code written incorrectly, and the shows the error messages you get from a VC++ 6.0, and GCC Linux compiler, and then she explains what the errors really mean, and how to fix them. The are also sections in the first few chapters that show common begginer mistakes, such as:

if(x=0) // should be (x==0)

or

A || B && C || D which is really
A || (B && C) || D because the compiler evaluates the && first

I recomend this book not only because I know if I had it when I was trying to learn, I would have had many less sleepless nights, but also because the author is an instructor at my school, and she is a really good programmer.

Hope this helps

I think, therfore I am.
I think?

I''d jot down all the books mentioned here and go to your local computer book store or major book store and look through those books and see which one you like more. It''s all mostly preference and your style of learning. Some dive right in, some pan things out more. Just sit down and skim through the first few chapters and read the introductions to those books and see which one fits you the best.


I know only that which I know, but I do not know what I know.