For your final project, you will write one of the four programs described below. You will work alone for this project. This does not mean that you shouldn't talk with each other and lab assistants about your project. It does mean that the bulk of your code should be your own, and that any assistance you receive from others should be acknowledged in the comments and documentation accompanying your code.

I: Poker Hand Probabilities

To do this, your program will generate a large number (many millions) of poker hands, and count the number of royal flushes, flushes, straights, full houses, etc. included among those hands. This means that you will need to figure out how to generate a random poker hand, and then how to determine what type of hand it is.

Your program should report probabilities for each of the following types of hands. The term "rank" refers to the card's numerical or letter value.

• Royal Flush: A, K, Q, J, 10, all the same suit.
• Straight Flush: five cards in a row (Aces are high), all of the same suit, but not including Royal Flushes.
• Four of a kind: any four cards with the same rank, plus any fifth card.
• Full House: three of the cards of the same rank, and two cards of the same rank. That is, three of a kind and a pair in the same hand.
• Flush: any five cards of the same suit.
• Straight: five cards in a row (not all of the same suit, since that would be a straight flush).
• Three of a kind: three cards of the same rank, plus two other unmatched cards.
• Two pair: two cards of any one rank, two cards of any other rank, plus one unmatched card.
• One pair: two cards of the same rank, plus three unmatched card.
• Other: any hand that doesn't fall into one of the above categories.

II: Moveable Movies

There's a catch, though. Your code should be organized so that the movie can be shown in a frame of any size or location. In particular, your code should include a function described as follows:

	//
	//	DrawFrame
	//
	//	Draws the Nth frame of the movie inside the rectangle
	//	the coordinates of whose top, bottom, and sides are
	//	given by the parameters top, right, bottom, and left.
	//	Note that no drawing is done outside this rectangle,
	//	and that no assumptions are made about the width, height,
	//	or ratio of width to height of the rectangle.
	//	
	
	void DrawFrame( int N, int bottom, int left, int top, int right );

There are lots of cute tricks you can play with your movie if you organize the code in this way. For example, you could show the movie in two locations on the screen simultaneously by doing something like this:

	for( int i=0; i < nFrames; i++ )
	{
		DrawFrame( i, 0, 0, 200, 200 );
		DrawFrame( i, 300, 300, 500, 500 );
	}

Or you might show all the frames simultaneously in one window, lined up in a grid so you could compare all the frames at the same time. Or you could draw a fancy border, and show the movie inside it.

You need not do any of these things with your code, but you should definitely test it in rectangles of various shapes and positions.

NOTE: DrawFrame should not call createwindow. In fact, your main program should call createwindow once, after which createwindow should never be called again.

III: Anagrams

For this project, you will write a program that gets a word or phrase from the user and prints out a list of anagrams. You may use the dictionary file /Accounts/courses/cs117-1/words.txt to provide data for your anagram hunt. Also, you may restrict your anagram search to single words rather than words and phrases.

Anagram finding is pretty tricky, and there are lots of ways to approach it, but let me give you one idea. You can compute something we'll call the "signature" of a word (or phrase, for that matter) by making an alphabetical list of the letters in the word. Thus, for example, the words "dear" and "read" both have the signature "ader." Perhaps you can put the signature idea to use.

IV: Boggle

For this project, you will write a program that generates a random Boggle board, prints it out, and then prints a list of all the words contained in the printed board using the Boggle rules. You may use the file /Accounts/courses/cs117-1/words.txt as the authority on what words are legal.

This problem is easy to state, but not so easy to solve. Good luck.

What to Hand In?

Grading Criteria

• Does it compile? I can't test it, and thus I can't grade it, if it doesn't compile.
• Does it work? Correctness is the most important thing, though by no means the only thing. Your program should work. If it doesn't do exactly what it was intended to do, you should provide a discussion of that fact in your documentation.
• Is it well organized?
• Is it well documented? Your code is a piece of writing directed to two audiences--human readers and compilers. You need to make the code readable to both of them, and clear commenting is an essential part of what you do for your human readers.
• Is it written with good style? Descriptive variable/function/parameter names, consistent indentation and placement of braces, and appropriate comments are the fundamentals of good coding style.

That's all

Start early, stay in touch, and have fun.