CS 4500 Assignment #4.
Assigned: Friday, 26 September 2014
Due: Friday, 10 October 2014

Working in an instructor-approved team of four students
(except for a few smaller teams approved by the instructor),
develop a rapid prototype of the greatly simplified version
of the semester project specified below.

Your prototype's source code must be written entirely by
your team.  Your team must not use source code written by
other students, must not use source code obtained from the
World-Wide Web or other sources, and must not use software
packages that are not already installed on the CCIS Linux
machines.

In exceptional circumstances, you may ask the instructor
for permission to use third party source code.  You should
not assume permission will be granted.

Your prototype must include a README file (which *must* be
in UTF-8 plain text, must be named README, and must not
contain any lines longer than 80 characters) that

1.  lists all members of your team,
2.  gives the preferred email address(es) for contacting
    your team,
3.  tells the grader(s) how your team's rapid prototype
    can be compiled and run on any CCIS Linux machine in
    the main lab,
4.  acknowledges any third party software used (by permission!)
    in your submitted software.

All of the files necessary to construct and to run your
prototype must be combined into a gzip'ed tar file whose
name ends in tar.gz.  Submit that gzip'ed tar file before
10pm on the date it is due using the submit script that's
described at the course assignments page:

    http://www.ccs.neu.edu/course/cs4500f14/assignments.html

Your prototype will be graded on these criteria:

1.  the quality of the instructions and documentation
    in your README file,
2.  the ease of constructing and running your prototype
    on CCIS Linux machines,
3.  your prototype's correctness with respect to
        parsing correct command lines
        recognizing and allowing the supported file formats
        reporting errors for unsupported file formats
        producing correct error messages
        not producing extraneous output
        not attempting to create files outside of /tmp
4.  your prototype's reliability with respect to
        reporting non-matches for audio recordings of different lengths
        reporting non-matches for recordings that don't sound alike
        reporting matches for audio recordings that sound alike
5.  and the readability of your source code.

Your prototype's build process must result in software that
can be invoked by cd'ing to the directory containing your
software's executable and executing a command of the following
form:

    ./dan -f <pathname> -f <pathname>

where <pathname> is a Linux path name that ends in ".wav" for
a file that already exists on the CCIS shared file system and
is in WAVE format with CD-quality parameters (AudioFormat 1,
stereo, 16 bits per sample, 44.1 kHz sampling rate).

Your software should not assume that every file whose name
ends in ".wav" is in WAVE format.

If the command line is correct and each <pathname> is correct,
then the dan program should compare the WAVE files to see
whether they are of exactly the same length and sound alike.
If so, then the dan program should print "MATCH" to standard
output, followed by a space, followed by the short name of the
first file, followed by a space, followed by the short name of
the second file, followed by a newline.  If not, then the dan
program should print "NO MATCH" to standard output, followed
by a newline.  In either case, the dan program should terminate
with an exit status of 0.

If the command line is incorrect, or a <pathname> is incorrect,
then the dan program should write one or more error messages
to standard error, each beginning with "ERROR" and terminating
with a newline.  After writing these error messages to standard
error, dan should terminate with an exit status other than 0.

----------------------------------------------------------------

/course/cs4500f14/Assignments/A4 contains a README file and
several test files.  Those test files are just to get you
started.  You will need to augment those test files with many
other test files.

The following examples assume you have copied the test files
into the directory that contains your dan program.

% ./dan -f z01.wav -f /course/cs4500f14/Assignments/A4/z01.wav
MATCH z01.wav z01.wav
% ./dan -f z01.wav -f z02.wav
MATCH z01.wav z02.wav
% ./dan -f z02.wav -f z03.wav
NO MATCH
% ./dan -f z03.wav -f z04.wav
MATCH z03.wav z04.wav
% ./dan -f z04.wav -f z05.wav
NO MATCH
% ./dan -f z05.wav -f z06.wav
MATCH z05.wav z06.wav
% ./dan -f z06.wav -f z07.wav
NO MATCH
% ./dan -f z07.wav -f z08.wav
MATCH z07.wav z08.wav

% ./dan -f z05.wav -f Sor3508.wav
NO MATCH

% ./dan z01.wav z01.wav
ERROR: incorrect command line

% ./dan -f z01.wav -f Sor3508.mp3
ERROR: Sor3508.mp3 is not a supported format

----------------------------------------------------------------