|CSC 161||Grinnell College||Spring, 2012|
|Imperative Problem Solving and Data Structures|
The purpose of this module is to smoothly integrate and review material that has been presented through the semester, with a particular emphasis on C programming concepts and full usage of the Scribbler robot.
|Tuesday, May 1||Module 7: Introduction|
|Wednesday, May 3||Command-Line Arguments||lab exercise|
|Friday, May 4||Files||
|Monday, Mon, May 7||Supplemental Problem 4 or Supplemental Problem 5||Supplemental Problem 4 or Supplemental Problem 5 (done individually)||Monday, May 7||Both problems may be done for extra credit|
|Monday, May 7||Files Continued||
||lab exercise||Friday, May 11|
|Tuesday, May 8||Module 7 Project Day 1||project||Friday, May 11|
|Wednesday, May 9||Module 7 Project Day 2||project||Friday, May 11|
Write a "robot logger" program which can log actions to a file, and also read actions from a file and perform them.
if the use specifies a command-line directive -w, then
if the use specifies a command-line directive -r, then
if no command-line arguments are given, the program should remind the user that the program requires -w or -r.
This program should support at least 10 different actions (following the module 3 project command requirements).
You are encouraged to use either your module 3 project or your command-robot.c program as the basis for the command input.
This project will be worth 25 points, based on the following rubric:
The program can write actions to a file. (5 points)
The program can read back the actions file and perform those actions in order as listed in the file. (5 points)
The program can be executed with the -w (write) flag and the -r (read) flag. (5 points)
There are at least 10 different robot actions supported, with either standard i/o or command-line input supported (5 points)
Code is well documented, reasonably efficient and well-structured, and example command files are given. (5 points)