CSC151.02, Class 36: Higher-Order Procedures, Continued

Admin
* Candy at front of room
* Exams due at 4:00 p.m. today.  Any final questions?
* No reading for Thursday.  Finish today's lab, if possible.

Overview:
* Review
* Lab
* Reflect

Review: What did you learn in CSC151 yesterday?
* Higher-order procedures are kinda lika shorthand way of writing procedures
* Higher-order procedures use other procedures as parameters
* Michael reiterates regularly
* Good programmers use higher-order procedures to encapsulate patterns rather than writing the same damn code again and again and again
* Good programmers use higher-order procedures to speed their programming
* select is "really cool"
* Procedures can be anonymous: They don't need names
* Sam has opinions

Do the lab!  Be prepared to reflect.  Ask questions

Today's list of things Sam hates ...
* (define square (lambda (x) (+ 1 (* x x)))) 
  * "square" is a bad name for what this procedure does
  * "successor-to-square" might be better
  * "f" would be okay
* Oge
  * "You asked for it, you got it"
  * Unable to form coherent arguments

See the examples page for ways to write make-tallier