Assignments

• You must name your program files pg##.cpp according to the assignment number and part, using all lower case letters. For example, the program for assignment 1, part A must be in a file called pg1a.cpp. These are the files your TAs will grade.
• You must turn in a printout of all assignment source code with all pages for that assignment stapled together.
• You must include the following information in a comment at the beginning of every file you submit: name, email address, local phone number, this course number (600.109), the date, your jhunix account name, the assignment number and part. If there is a problem with reading your program file, a TA will contact you via email.
• All programs should have a short comment at the beginning describing their purpose. Feel free to include complete pseudocode as well.
• You must use good programming style, including descriptive variable names, spacing and indentation where appropriate, and comments to explain related code segments.
• Graded programs will be returned in class on Mondays a week after they have been turned in. Anything not picked up in class can be picked up from Dr. Houlahan, NEB 224.

Until a due date is listed below, expect the assignment to be UNavailable.

• Assignment #1 -- due Wed, 2/9
• Assignment #2 -- due Wed, 2/16 -- solution (for help with assignment 3 if necessary)
• Assignment #3 -- due Wed, 2/23 -- solution
• Assignment #4 -- due TUESDAY, 3/1 -- solution
• Assignment #5 -- due Wed, 3/9 -- solution
• Assignment #6 -- due Wed, 3/30 -- solution
  Assume the mazes are at most 30x30 in size. Here are some samples: maze1.txt, maze2.txt, maze3.txt, maze4.txt, maze5.txt. Here are corresponding solutions:moves1.txt, moves2.txt, moves3.txt, moves4.txt, moves5.txt.
• Assignment #7 -- due Tue, 4/5
• Assignment #8 -- due Wed, 4/20 -- pg8a.cpp driver (tester) program
• Assignment #9 -- extended to FRIDAY NOON, 5/6, turn-in printouts to NEB 224