The OOT code

For the array implementation:

file appt.tu
file appt.tb
file Copy procedure for appt.tb <-- added Mon 03 Feb
file apptcal.tu
file apptcal.tb
file time.tu
file time.tb <-- revised Wed 29 Jan
file main.t
Sample data file apptcal.dat

For the linked list implementation: For the linked list implementation:
The files are now available directly from this web page.

file apptcal.tu (linked list version)
file apptcal.tb (linked list version)
file queue.tu
file queue.tb

The apptcal files are different, of course, because the implementation is changed here from array to linked list. The queue files implement the queue ADT, which you need to use in this implementation's view-week code (as described in the handout).

About the OOT code

You will notice that in both the appt.tu and time.tu files, the word "opaque" occurs in the export list. For example:
```
    export opaque ApptType, maxMessageWidth, Empty, ...
```
The "opaque" is a keyword in OOT, and it applies only to the next item, in this case ApptType. Why is it there? ApptType is exported so that the user of this module can create as many appointments as needed. But it is exported "opaque" so that the user of the module can only talk about things of type ApptType. The user of the module cannot itself look into things of this type, for instance to set or examine a field of the record. (Exported routines provide these operations instead.)
There virtually no error checking of the input to the program. You do not have to improve this. But you may find it annoying that the program will crash if you make a typing mistake while running it. Feel free to improve the error checking. (There is no need to hand this in.) Do not change anything else about our code.