Program 1: Common Lisp

Solution

Here is the test file, tester.l.
Here is a sample solution, go.l.

Due Date

This assignment is due at the beginning of the lecture on Friday, September 21st.

Partners

Everyone should complete this assignment with one partner. Submit one solution with both of your names on it.

Purpose

The purpose of this assignment is to give you practice solving problems in Common Lisp.

Gomoku

Read the rules for Gomoku. Gomoku will also be the basis for the Program 4 game playing tournament.

Assignment

Write a Common Lisp function named five-in-row-p (and any other auxiliary functions that are needed) in a file named go.l. The function should return t (true) if the last stone played results in a win and nil (false) otherwise.

The function five-in-row-p should make no assumptions about the size of the board that it is being passed. For example, the board might be the standard 19 by 19, but it might also be 10 by 12. However, the function may assume that the coordinates of the last move played are valid ones.

Starting Code

Take a look at the file tester.l. If the five-in-row-p function is coded correctly, the following output should be produced when (test) is typed into the Common Lisp command prompt:

Win for WHITE playing at (0, 3)
Win for WHITE playing at (0, 6)

What to Submit

The following materials must be received on or before Friday, September 21st at noon.

A printout (not an e-mail) of the go.l file that contains the five-in-row-p function.
An e-mail of the go.l file to John at paxton@cs.montana.edu

Grading

10%. The go.l file compiles with no errors and no warnings. Furthermore, the go.l file should not contain any of the functions that are provided in the tester.l file.
60%. Correctness. I will test your go.l file on an undisclosed sample test set of my choosing. Thus, it is very important that you anticipate and test your solution thoroughly before submitting it. Also, you will want to make extra sure that no run-time errors can occur.
20%. The quality of the solution. Does your solution use Common Lisp appropriately? Does the solution avoid duplicated code? Is the solution elegant? Is the solution easy to read and maintain? etc.
10%. The solution is commented appropriately. The document includes a file header comment, function header comments, tricky code comments, local variable comments, etc.