head	1.5;
access;
symbols;
locks; strict;
comment	@% @;


1.5
date	92.12.14.09.45.05;	author lacey;	state Exp;
branches;
next	1.4;

1.4
date	92.12.14.03.11.51;	author lacey;	state Exp;
branches;
next	1.3;

1.3
date	92.12.14.02.23.39;	author gaubert;	state Exp;
branches;
next	1.2;

1.2
date	92.12.14.01.24.38;	author lacey;	state Exp;
branches;
next	1.1;

1.1
date	92.12.14.01.17.54;	author lacey;	state Exp;
branches;
next	;


desc
@@


1.5
log
@*** empty log message ***
@
text
@\section{File Read/Write Subsystem}
A known bug in the Read/Write file subsystem is that the read-file
routines will not be able to recognize the task names or descriptions
that contain a ' '' ' within the string.
@


1.4
log
@*** empty log message ***
@
text
@d2 1
a2 1
A known bug in the Read/Write file subsystem is that the readfile
d4 1
a4 1
that contain a ' '' ' within the string.
@


1.3
log
@*** empty log message ***
@
text
@d1 1
a1 1
\subsection{File Read/Write Module}
@


1.2
log
@*** empty log message ***
@
text
@d2 3
@


1.1
log
@Initial revision
@
text
@a1 10
%
% If your testing specifications were correct, then you can
% include the text for the test data description and expected 	
% results. Otherwise, incorporate the corrected descriptions.
%
\begin{description}
\item[{Test Data: }] 
\item[{Expected Results: }]
\item[{Actual Results: }] 
\end{description}
@
