Week 04 Notes for CS 1500, Section 002 -- Spring 2001

• Class starts at 11:15. I take roll at 11:25
• Announcement(s)
  • Solo Program Due Wednesday
  • Lab # 03 on Friday
  • Quiz next week -- Friday, Mar 16
  • Rules in lab will get more strict:
    • If you won't be able to attend a lab at the scheduled time then request to be excused at least a day in advance. Otherwise, you may not get credit for performing the lab -- even if you do the work later.
    • Work with your partner. If you don't work with your partner, you may not get credit for performing the lab.
    • Follow the directions for the lab very closely. When in doubt as to the meaning of the directions, ask. If you don't follow all the directions, you may lose points.
• Handback Lab 01 printouts and announce location of online grade info
• Grades for Lab 02 have been posted. Look at two reports: "Grades" and "lab02ResultsByCode." Look at the second file to see notes about errors. Be careful because labs will get a little harder and grading will be getting more strict. On Lab 02 one team made an error and failed to send the source code. They should send it right away and I'll excuse the lateness.
• There is one group of one and one group of three. I want to make two groups of two.
• Take care of e-mail matters:
  • Show everybody how to use the -v option and how to send a copy of an e-mail message to themselves when sending mail "from the command line"
  • Show an example of sending mail interactively.
  • To be sure that I get your e-mail message:
    • Use the -v option.
    • Include yourself as a recipient.
    • Look carefully at the output resulting from the -v option to verify that the message has been delivered to me.
    • Read your own mail to make sure that the correct message was sent to you (and me).
  • For more information about sending and receiving e-mail, see chapters 18-20 of the Andersen text book. Also you may use the Unix man command (e.g. "man mail") to find out more about mail (aka mailx).
  • ANNOUNCEMENT: From now on, failure to send part of an assignment by e-mail on time will incur a significant penalty. Be careful.
• Discuss the way that function calls are implemented -- the runtime stack -- look at "runTimeStack.cpp" and "runTimeStack.jpg"

• Class starts at 11:15. I take roll at 11:25
• Announcement(s)
  • I posted directions for Lab #3. Study and rehearse.
  • I posted assignment of Solo program #2. Read directions.
• Handback Lab 01 printouts.
• Show an example of a recursive function.
• Discuss lab #3.
• Look at "my_example.cpp" and "sample1.cpp"
  • Go over material to test understanding of operator precedence (typical quiz topic)
  • Examine the use of functions.
  • Note how top-down design is used to organize a program into a set of simple functions (rather than a single, complicated function.)
• Further topics related to function calls:
  • how value parameters are passed
  • why an expression can be used as an actual value parameter
  • The fact that a variable can be used as an actual parameter when the name of the variable is not the same as the name of the formal parameter.
  • understanding the scope of a local variable.
  • understanding that a called function cannot change the caller's copy of a parameter passed by value.
  • global variables are special: visible everywhere except where they are "masked."
• Lecture topic: ADT's and classes: what are they and what are they good for?

• Class starts at 11:15. I take roll at 11:25
• Announcement(s)