This entry was posted in Lesson by dgookin.

I may complete this task one day when I’m bored, but I’m rarely bored.Ĭlick here to view the full code on Github. That way the cards can be displayed graphically (well, in text mode) and the program can truly be interactive. If I were to modify the game further, I’d code it in Ncurses and use a full terminal window display. You could add a routine to draw a second hand for “the computer” and pit player’s hand against the computer’s. But given what I have now, the code could be modified to be more interactive, to allow for cards to be discarded and new cards drawn. Don’t worry! I’m not going to extend this series one more Lesson.

This outcome is the disappointing part.Īt this point, the code can be modified further. I ran the program over and over and the best I saw was three-of-a-kind. Getting a flush or full house is truly rare. Single pairs may also appear, but mostly you get a lot of high-card hands. The output you see above is most typical. Your hand is A♣ 6♦ 8♥ K♣ 9♦ - High card: A♣ Wprintf(L' - High card: %s%lc ',hand.face,hand.suit) So I fixed up the relevant part of code: /* account for ace as the high card */ Whoops! I noticed that my high-card if test doesn’t count for the value of an Ace as 1, low. You can see that the output is unsorted, through internally the code sorts the hand by card value, which is what the various evaluation functions expect. I think the code is nifty, but the output shows you how long the odds are on a typical 5-card hand of poker. With all the hand-ranking functions complete (see last week’s Lesson), the final version of my poker program restores the randomizer, draws and sorts a hand, then outputs the hand’s value.

5 card poker scoring