Summary of style recommendations to date:

- provide header for course
- optional header: Chapman's recommendation for revision record
- list *major* variables and their meanings/descriptions 
  below the header(s)
- comment all control structures
  + comments should indicate what happens overall--not what every
    step will do
  + comments should go above the block
- where do comments go, in general?
  + for a line, comments go to right (can be above, too)
  + for a block, comments go above
- things to avoid:
  + comments that do not reveal new info (sorry--like the ones below--
    just in case you are actually doing this)
  + comments that are so specific they mimic the code
  + comments that are too wordy

Not everyone agrees on the best style. The rule of thumb is to pick
something generally acceptable and be consistent.