This lab requires you to flesh out the very detailed API that I have already given you, to produce a working system. It should produce results similar to the two I have posted, demo1 and demo2, showing the cars in successive printout lines moving to the right, with successive lines at later points in time. The extensive comments that I have included in the API should tell you what you need to do. (Those of you who were fortunate enough or sensible enough to be in class on Thursday the 15th saw me go through my entire working code for this lab, mostly via my computer and the projector, now in excellent focus.)

This page explains what you are to do and turn in for this assignment. The background and details for the lab are in the details page. The lab took place on Tuesday, February 13^th and is due by 4pm on Monday, February 19^th.

WHAT YOU ARE TO DO AND HAND IN FOR LAB 6

1. What you are to do was laid out fairly extensively in the Lab 5 assignment. The major difference here is that instead of prototypes, you are to flesh out all classes and functions with full contents, compile and run the code and produce output showing your cars in motion, interacting.



2. To make the design and implementation less burdensome, you are welcome to make all members of your classes public and write no member accessor functions. You could do all your work in a single file for Lab 5, if you chose to, but for Lab 6 you are required to have your project in multi-file form, using separate compilation, as for Lab 4.



3. For Lab 6 you must hand in hardcopies of all you source files, including your output prints of the cars in motion. If you have written your output to separate files, these files should be included on your floppy in addition to hardcopy.