CS 5500 Assignment #5.
Assigned: Wednesday, 2 October 2013
Due: Wednesday, 9 October 2013

Working in an instructor-approved team of four students
(except for a few smaller teams approved by the instructor),
develop a rapid prototype of a program that checks command
line syntax and file formats according to the specification
given below.

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

Your prototype must include a README file (which *must* be
in UTF-8 plain text, and must be named README) 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/cs5500sp13/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.  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:

    ./arc5500 <pathspec> <pathspec>

where <pathspec> is a sequence of tokens generated by

    <pathspec>  ::=  -f <pathname>
                  |  --file <pathname>
                  |  -d <pathname>
                  |  --dir <pathname>

and <pathname> is a Linux path name for a file (in the -f and
--file cases) or directory (in the -d and --dir cases) that
already exists on the CCIS shared file system.

If the <pathspec> uses the -f or --file options and names a
file, that file should be in WAVE, mp3, or Ogg Vorbis format.

If the <pathspec> uses the -d or --dir options and names a
directory, then every file within that directory should be in
WAVE, mp3, or Ogg Vorbis format, and that directory should not
contain any subdirectories.

Recognition of the WAVE, mp3, and Ogg Vorbis formats should
not rely on file name suffixes.

If the command line is correct and each <pathspec> is correct
with respect to the criteria listed in the paragraphs above,
then the arc5500 program should produce no output at all and
should terminate with an exit status of 0.

If the command line is incorrect, or a <pathspec> is incorrect
with respect to the criteria listed above, then the arc5500
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,
arc5500 should terminate with an exit status other than 0.

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