Follow these guidelines for your projects, otherwise they may lose points or be completely rejected.

1. Write your code in C or C++.

2. You can code your projects on any system but before you submit them make sure they compile and run successfully using some compiler on some UNIX or LINUX machine in the CS department.

3. Each project should have one input file and one output file. Each project will be tested with a number of different test files so don't hard-code file names in your project - allow the user to specify them using one of these three schemes:
   • Command Line Arguments: a.out infile outfile

   • Re-directed I/O: a.out < infile > outfile

   • Prompts:

     a.out
     Enter input file name:	infile
     Enter output file name:	outfile

4. Assemble all the parts of a project into one program file. Use #include directives only for standard system files like <stdio.h> and <iostream.h>. Don't submit makefiles.

5. Write a comment at the beginning of your program file with at least the following information:
   • Your name
   • The project number
   • The name of the machine in the CS department that runs your project successfully.
   • The name of the compiler on that machine that compiles your project successfully and a list of any compiler flags that must be used.
   • The scheme to specify file names: Command Line Arguments, Re-directed I/O, or Prompts.

6. Don't use any Microsoft program to send me your projects - they tend to encode attachments so only another Microsoft program can read them. Use mail on a UNIX or LINUX machine in the CS department to submit a project:
   • Enter mail batcher (add your own userid to also mail it to yourself.)
   • For the subject enter Project and the project number.
   • For the body of the message enter ~r filename where filename is the name of your project code file.
   • mail displays the number of lines and characters in the file to show it was inserted.
   • Enter a single dot (.) to exit mail.