Don't forget to comment your programs. At the top of the program put a comment block identifying yourself, what class the program is for, the date, etc. Blocks, paragraphs, groups of code should be commented as to their function.
The output of your program should show clearly that it is working correctly. Put write statements at strategic places in your program to show that it is working correctly. This kind of output will be immensely helpful to you for debugging, anyway.
Run your program with several different sets of test data.
Your program grade will be based on: following directions, correct operation, quality documentation (comments in the code and your attached write-up), modularity, code clarity and quality, thoroughness of testing, doing your own work according to the guidelines in the syllabus, and error checking and handling.
In addition, you are to include a write-up describing the following.
Use the `submit' command shown in class to turn in your programming assignment electronically so I can run it. Use directory `Pr1' for the first assignment, `Pr2' for the second, etc. You must `submit' all program source file(s), all sample input file(s) if any, all sample output file(s), and your write-up file.
The submit command will not accept for electronic submission any file containing ``control'' (non-printing) characters. Unfortunately, control characters are put into the typescript file produced by a script session, used to record sample runs in a programming assignment. These control characters must be removed before submission. The way to do this with the vi editor is as follows.
% vi typescript :1,$s/^V^M//g :1,$s/^V^H//gAfter vi starts up, you enter two ``colon'' commands. The notation ^X where X is V, M, or H means control-V, control-M, and control-H. The control-V escapes the following control-M or control-H in the command so it is entered literally. Extra-credit, if any, MUST be submitted at the same time as the base assignment.