W4118 Spring 2013 Programming Assignment

Assignment Number:
   
Group Number:

Name and UNI of Group Member 1: _________________________
   
Name and UNI of Group Member 2: _________________________

Name and UNI of Group Member 3: _________________________
   

We certify that:
   	   _ Our code compiles and works for all reasonable inputs
	   _ Our code compiles, but does not work for all inputs
	   _ Our code does not compile

    * While we may have discussed the assignment with others, the code
       submitted is entirely our own group's work and no other student 
       has edited it.
     * So far as we have been able to determine, the program properly
       handles all reasonable inputs.

   Further instructions to the student: 
     * Check your code to make sure it is readable. You may wish to
       add some comments, change a variable name, or even restructure the
       code. This also often helps you find bugs in the code.
     * Include this file with the files you submit for your
       programming assignment.  The file should be named  "pg_cover.txt".

     * Describe below how each member of your group contributed to the
       assignment.  Include a list of C functions and files that you modified
       or implemented and which group member was primarily responsible
       for doing each.  All group members are expected to contribute in
       writing the code for each assignment.
       
Member Contributions:








If your program does not work for all test inputs or does not compile,
please complete the following section. You should describe below what 
the bug is and how you tried to debug it. Document only the most
significant bug. This is you chance to get partial credit for code
that does not pass testing. If you do not make a good faith effort to fill this
section in when you know your code doesn't compile/work, you may
automatically be given a zero for those parts of the assignment

     * Describe the conditions that cause the program to fail. For
       example, you may know that it always fails for a particular input
       or kind of input. Or you may know that it always fails when try it
       for the second time, or when a certain procedure gets called with
       a certain argument or when a particular global variable has a
       particular value.
       
     



     * When the program fails, what error message or other output does it
       generate?
       
     
     
     
     * What does the error message mean? 
       
     
     
     
     * When the program fails, which of your procedures is it running?
       
     
     
     * In your source code, put comments /*** Buggy code here ***/
       around the line that it is executing when it fails. Describe
       below how you know that this is the right line.  If you can't 
       determine which line then put BOLD comments around the 
       different possible lines it could be executing. 
       
     
     
     * Do you believe the bug is in this procedure? If not, do you think
       it's in a procedure that called it, or in some procedure that was
       executed previously and that either returned a bad value, or that
       placed a bad value in a variable someplace? Why? Note: we're not
       asking you to get this right. We're just asking you to give a
       plausible answer with a plausible justification, enough to show
       that you're developing sound reasoning processes for diagnosis.