Laboratory Exercises

This course includes weekly laboratory exercises, as listed on the course schedule.

For more information about how to prepare for and complete lab exercises, see the discussion under Course Mechanics.

• Unless otherwise stated,

  • collaboration IS allowed on laboratory exercises.
  • you may use language references to determine relevant C syntax and semantics. Since C syntax is standardized, we will consider C syntax and semantics to be "general knowledge", and you need not cite your reference sources.
  • you may consult only the textbook and the C syntax references for information regarding alorigthms. All non-syntax consultations (including the textbook and C references) require formal citation within the related program or exercise.
• You always may consult the instructor regarding questions on labs or assignments (at least if the instructor is in her office with the door open).

• Programs are to be submitted in the program format given below.

Submitting Programs For This Course

In turning in any programs for the course, please follow these directions:

1. The first seven or more lines of any C program should be comments containing your name, your mailbox number, your lab section, an identification of assignment being solved, and a description of the contents of the file. For example:
   

    
   /*************************************************************************
     * Janet Davis
     * Box Science II
     * Laboratory Section 213L.04
     * Lab 1: Review of C; Sorting and Order Statistics
     * arraylib.c: Definitions of useful functions to manipulate arrays
     ************************************************************************/
   

2. Also, a comment is needed for every definition of a C function, stating in English what that program unit is supposed to do.
3. Obtain a listing of your program and a record of relevant test runs using the script command:
   • Within a terminal window (before running C), begin recording session with the statement
     
     script filename
     
     where filename is the name of the file in which you want the session stored.
   • Within the script file,
     • Print a copy of your program with the command
       
       cat C-file.c
       
       where C-file.c is the name of the file containing your C program.
     • If your work involves several files, list the main program first with the cat command; then list any supplementary files.
     • Compile your program with the gcc command, and run it with appropriate test cases to check the correctness of your program.
   • When your runs are complete, stop the script session by typing <Ctrl/D>.
   • Print the record of your session by typing
     
     enscript filename
4. Either write on your printout or include a separate statement that argues why your program is correct, based upon the evidence from your test runs.

Notes on Grading

• Since every programming task should yield readable and carefully tested code, the grading of all programs for this course will begin with the following algorithm (expressed in C format):
  

   if ((no_comments)
       || (no_evidence_of_compilation)
       || (no_test_runs)
       || (no_commentary_on_correctness))
       return (no_grade);
  

• When a program is submitted accordin to the format specified above, it should be understood that the program listing reflects a complete session of program listing, compilation, and running. With this understanding, editing of any script file is strictly forbidden and will result in automatic failure on the assignment. Such editing also may raise questions of academic dishonesty; and, by College policy, any evidence of academic dishonesty must be turned over to the Academic Standing Committee for action.

Janet Davis (davisjan@cs.grinnell.edu)