\begin{singlespace}
\begin{center}
\Large
CSCI 161 Programming Assignment 3 (Spring 1996)\\[1em]
\normalsize
\end{center}
\noindent
{\bf DUE:} On or before 11pm Wed March 6.\\[1em]
{\bf PROBLEM DESCRIPTION}\\[1em]
Implement the {\tt DISet} module according to the module
interface specification in \\
{\tt ~pwalsh/161.open/DISet}.

Be sure that you make no changes to {\tt DISetInt.p}. 
You must use a linked list to store the elements of the set.
Note, the access routine {\tt DISInit} does NOT have to dispose of any memory
associated with an existing list.
The access routine {\tt DISDel} must dispose of the memory associated with
a deleted element. \\[1em]

\noindent
{\bf EVALUATION CRITERIA}\\[1em]
Your implementation will be graded on the basis of its run-time behaviour and on the clarity and simplicity of the
source code.
Your implementation must have no side effects,
including file input or output.
We have compiled a set of test cases. 
Your implementation 
must operate correctly on all of our tests to receive any credit for run-time behaviour. 
With regard to simplicity and clarity, follow the ASAP principle: as simple as possible.\\[1em]

\noindent
{\bf SUBMISSION}\\[1em]
This assignment is to completed by each student.
E-mail the file \verb+DISetImp.p+ to \verb+pwalsh+ (on {\tt malun1}). 
It should contain your implementation of \verb+DISetInt.p+.  
Submit only one implementation; if 
you send more than one, we will discard all but the {\bf last} one.

The assignment identifier is {\tt 161pex3} (see Course Information Sheet).
Your assignment  must be submitted before the due date and time.
In addition, your e-mail {\bf must} have the assignment identifier
as its subject.
All other methods of submission will not be accepted.
You will receive no credit
for an assignment submission that fails to adhere to this convention.



\end{singlespace}
