• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

What comes next?

Blacks

n00b
Joined
Jul 8, 2011
Messages
4
Hi,

I have been reading a book and helped me allot about C++
So far i have covered:

-Types, Variables, and Standard I/O
-If Statements, branching and Looping Statements
-For Loops, Strings, and Arrays
-The Standard Template Library (vectors, iterators, algorithms etc..)
-Functions
-References
-Pointers
-Classes
-Advanced Classes and Dynamic Memory
-Inheritance and Polymorphism

I feel very comfortable with the above topics except sometimes i feel lost for a second when the word comes to pointers but i am getting much better at it- (repetition is the mother of learning :p)
And now as i finished the book i am not sure where to continue after this.

First of all i should say that i would like my feature project to be "poker bot"
that means.
Extracting data from other programs
bit of more advanced AI to know how to play
Introduction to c++ visual programming (the interface)
databases to store the played hands, read databases etc..
(who knows what else.. i guess dll injections as well).

I would like to know if there is such a book(s) that would prepare me for these kind of stuff? I have searched the net for these things but it's just so hard for me to make a choice without some bit of advice :)

Thank you.
 
Since you're working with a well known and documented topic (ie: poker rules), then just start with implementing the game: the cards, the play order, storing game progress. If you're not yet comfortable with programming AI, then write the game as requiring two or more people.

Alternatively, you could change from writing a poker to writing a blackjack game. Many have rules on when the dealer must and cannot hit (such as "hit on soft 17, but stops at hard 17"), so that creates a simple play logic to implement.

Either way, I'm sure you'll still find many points of refactoring and restructuring as the game is developed.
 
Back
Top