I guess it's time for what I want to call my mid-C++ book, what next post. No I'm not saying that I'm stopping halfway to ask what I should focus on C++ wise, but rather well, everything else wise. Let me explain, after reading other books (C++ for dummies, C++ in easy steps) in which I was dissatisfied, I picked up "Beginning Game Programming In C++" because of the good user reviews on this site. Before I continue let me give you my "background story". My goal is not to, make a game fast. My goal is not even to make a good game. My goal is to learn, making a game will only aid in that process. Like many here, I'm just a 16 year old hoping to become a game programmer. While I do know about, C#, Python, Lisp, and all the other languages used to only create programs, but to create games as well, I always assumed it would be best to dive into C++ as a first (aside from some DarkBasic experience) language. It seems relatively easy so far, but I'm not foolish enough to think that it won't get much harder logic wise. I guess my first question is, with my goals in mind, what is the right thing to do? Which language should I learn first? Am I setting myself up for frustration with C++? My second question: If I do end up continuing with C++, what’s after the basics? Win32? SDL? openGL/DirectX (I'm assuming not). If you need me to explain something further, don’t hesitate to ask. Thanks a bunch in advance.

Quote:Original post by kevtimc
, C#, Python, Lisp, and all the other languages used to only create programs, but to create games as well,

This was a stupid thing to say, what I meant by this was something along the lines of great Win32 programs and games.

Excellent response, I was think of going into SDL as well. I guess I'll also continue with C++ for now.

Quote:Original post by gan

Quote:
I guess my first question is, with my goals in mind, what is the right thing to do? Which language should I learn first? Am I setting myself up for frustration with C++?

My second question: If I do end up continuing with C++, what’s after the basics? Win32? SDL? openGL/DirectX (I'm assuming not). If you need me to explain something further, don’t hesitate to ask. Thanks a bunch in advance.

Go and try out the game accompany with this book; then u know how great the book is . Then u know what differentiate pro and novice. Then u will never be frustrated with C++.

I think a full on FPS is out of my league, but thanks, I'll keep it in mind when I get much better.

Quote:Original post by Telastyn

Quote:
what’s after the basics?

Why, the intermediates...

Seriously, learn the language thoroughly first. Don't escew inheritance, templates, the Standard Library or even a common library like Boost because you think you know 'enough'. More tools means you'll have an easier time solving problems.

Along the way you'll realise what an asset it is to learn/practice application design, which will generally lead to Design Patterns and similar theory. That will help you greatly, since even 'simple' games are fairly large constructs, requiring effective design to build them acceptably.

Then you'll be in a good position to put the rendering APIs you mentioned to good use. Sure, you can probably learn them earlier, but [imo] not well. This applies similarly to other languages if you don't want to learn via C++ (which I'd perhaps not recommend) though perhaps less so since most other languages lack some of the nuances and pitfalls C++ has.

Ok, I have one question, how should I approach STL? My book covered vecotrs, iterators, algorithms, and a bit more, but every book is different.