NOTE 1: Always check your code with the Unit Tester and the Lisp Critic before submitting. Even the project, where there are no unit tests, can and should be checked with the Lisp Critic. Unchecked code will be returned unreviewed.

NOTE 2: Type your function definitions into a file editor window, not the Lisp Listener window. Using the Listener window produces badly indented code with tab characters. (See http://xarg.net/writing/tabs for why tab characters should never be in code.) You also lose your code when you leave Lisp.

Exercises are like calisthenics. Everyone needs to do them, but at their own pace and in their own order. They also help me get a measure of what you know (see the rules on grading).

These exercises are to give you practice in basic and advanced Lisp programming, as well as AI programming.

Your goal for this course is to prove to me that you're a good AI programmer. That means showing that you know how to apply the major tools of Lisp to AI problems. The best way to do that is to

Don't put off the Project exercises! Mix them in with the book exercises as soon as you've done the first 5 basic chapters of Graham.


checked with XENU button Valid HTML 4.01 Strict

Comments? Comments icon Send mail to Chris Riesbeck.