   Beginning C++ Game Programming question
That would be this book right here.Hello all.  I'm very new to game programming and perhaps a little slow, but I seem to be having some trouble with the exercises at the end of this book's chapters.  Are there solutions to these exercises readily available somewhere?  I tried contact the author at his site, but got an error message while doing so.Thanks for reading.   
  Perhaps you could post the specific exercises you are having trouble with? A lot of people around here could help you if they had the book, but I, for one, don't.   ;  What could you possibly hope to achieve by having the answers given to you? The point of the exercise is to help 'you' become familiar with the programming language that your using. You will learn nothing just by reading the book + therein source code. Dont be so lazy and attempt the excersizes, if you dont understand how to complete them you missed something in the chapter so go back and read it again... When you find what you couldnt understand you could try researching the topic elsewhere - google is a good start. :)don't be embaressed by the fact that learning to program is taking its sweet time, its the same with everyone (though some dont like to admit it). You dont become an accomplished painter/musician over night, this is also true for programming.   ;  Also, if you get hung up on one idea or concept and can't seem to grasp it, just ask for help on the forums.  There are tons of people who would be more than happy to help you out.   ;  Windryer - many exercises in the book refer to exercises in a previous chapter.  Then again, most of those said earlier exercises are basic generic stuff.  The word beginner is in the title, after all.CodeCriminal - I kind of thought the same thing, but if I get the general jist of a concept, but perhaps have a hard time applying it, maybe seeing the source code in action could give one of those "Eureka" moments ("so that's how it's done").  Not fully sure how well this will work for me, though.  Figure I'd give it a shot.I was concerned about flooding the message board with my questions.  Other boards might not take too kindly to such a blitz of pesky questions.  Though it's good to see that at least from here, this won't be a problem.  I suppose i'll be a bit more specific later on when I have access to the actual book.   ;Quote:I kind of thought the same thing, but if I get the general jist of a concept, but perhaps have a hard time applying it, maybe seeing the source code in action could give one of those "Eureka" moments ("so that's how it's done")Here's the thing, programming involves you being able to construct the code. Not just read. Programming isn't about knowledge. It's about problem solving, and to learn you must solve problems on your own. Looking at a solution does not build your problem solving skills.You're not going to be an exception. Every experienced programmer here learned by crunching problems by themselves. You have to do the same.   ;  im pretty new to programming (almost 2 years now), so trust me when is say this:programming is just one of those things where you learn much better an quicker by actually doing it!i used to all the time just "read" over stuff or look at example code and then think "yeah i get it". instead of actually doing it. i did this a lot for what seemed like the most trivial of problemsthen when you do need to implement it into something, you just "forget" and have no idea where to begin with! and then you have to go back and re-read everything.remember. if it was that easy, they wouldnt ask you to do it :)