PART I: MIDTERM DISCUSSION
==========================
Highest: 95/100

PART II: MAKEFILES, CONTD.
==========================
(1) Continuing on http://www.eng.hawaii.edu/Tutor/Make/index.html and then onto
CSV (again) http://www.udel.edu/CIS/181/sundaram/06J/lect/l7/workoutProject1/

(2) The "fields" in a struct are also called "members"

struct Workout_S
{
  char date[DATE_LEN];
  int meters;
  double splitTimeSeconds; // store the field in pure seconds
  int minutes;
  bool personalRecord;
};

The members are date, meters, splitTimeSeconds,
   minutes, personalRecord.

Declaring a struct allocates NO MEMORY.

Only when you use the struct to declare a variable
is any memory allocated, e.g.

 Workout_S myWorkout;  // scalar

 Workout_S januaryWorkouts[31];  // array


Scalar means "a variable that only holds
   a single value, i.e. not an array"


(3) Test Driven Development or TDD


TDD is a "big buzzword" these days in Software Development



***
  We will work all the way through the TDD process on testComputeSplitTime,
  culminating in a version of computeSplitTime.cc in a separate file,
  that works in combination with testComputeSplitTime5.cc

   So we combined 
          computeSplitTime.cc

   and
          testComputeSplitTime5.cc

   by using separate compilation, as follows:

    CC -c computeSplitTime.cc
    CC -c testComputeSplitTime5.cc
    CC computeSplitTime.o testComputeSplitTime5.o -o foo

 ./foo then produces

    Passed
    Passed
    Passed
    Passed

Next Steps:

    Go back to what we were working on originally, but
    organize it using a Makefile.

    We'll do that in the directory workoutProject1