Week 05 Notes for CS 2500, Section 001 -- Spring 2001

• Check schedule
• Class starts at 10:10. I take roll at 10:20
• Announcement(s)
  • Program #1 has been graded. Check postings and e-mails
• Take questions on program #2
• Look at how the operations work in the listClass.

• Look at Upcoming Schedule
• Class starts at 10:10. I take roll at 10:20
• Announcement(s)
  • Bring a blue book to class next time -- small size
  • I will be away on Monday, March 19. Work on programming assignment #3 in the lab that day.
• Documentor's thought for the day. The "boss" gives a copy of a function header plus function prototype to a programmer, and also gives the same information to one who will call the function -- the client. After that the programmer never has any contact with the client. The programmer writes the function according to the specifications in the header and the pattern of the prototype. Later the client makes many calls to the function without ever seeing the code for the function. Everything goes perfectly. The client knows just what to expect each function call to do, and each function call does what the client expects. If a header is written properly, then the scenario described above should be do-able. If the scenario is not possible, then there is something wrong with the header comment -- something is missing.
• Discuss programming assignment #3
  • Read some specs
  • Work on declaring a client record data type
  • Do an example compilation
• Discuss virtues of abstract data typing and modular code.
  • Easier to design correctly
  • Easier to change implementations
  • protects integrity of data from users
  • Easier to re-use code
• Look at the data structures talk

• Look at Upcoming Schedule
• Class starts at 10:10. I take roll at 10:20
• Announcement(s)
• Quiz today