CSc 372 Archives

• Fall 2001 ML mid-term exam and solutions. 45 minutes; 100% ML. With the exception of one student, who finished it after about 25 minutes, grades were relatively low on the exam. I don't know if the exam was too hard or I just didn't give students enough practice with the material on assignments. The average on this exam was 58.9.

• Fall 2001 Icon mid-term exam and solutions. 45 minutes; 100% Icon. The average on this exam was 80.2.

• Fall 2001 Prolog mid-term exam and solutions. 45 minutes; 100% Prolog. The average on this exam was 83.

• Fall 2001 final exam and solutions. 110 minutes; about half Emacs Lisp and half comprehensive. The average on this exam was 91.8.

• Fall 2001 Assignment 8 -- essay questions.

• Spring 1997 mid-term exam and solutions. 75 minutes; 50/50 ML and C++. This exam was "about right".

• Spring 1997 final exam and solutions. 2 hours; mostly Icon and Prolog with a little bit of ML and C++. This exam was "about right".

• Fall 1996 mid-term exam and solutions. 50 minutes; 50/50 ML and C++. This exam was way too easy!

• Fall 1996 final exam and solutions. 2 hours; mostly Icon and Prolog with a little bit of ML and C++. This exam was "about right".

• Spring 1996 mid-term exam and solutions. 75 minutes; 50/50 ML and Icon. This is the first exam I ever wrote. It was way too long, about an exam and a half, but two of the poor devils scored in the 90s. One of them was a graduate student studying genetics who had almost no programming experience prior to 372. I didn't have any trouble finding something good to say when he asked me to write a letter of recommendation.

• Spring 1996 final exam and solutions. 2 hours, mostly C++ and Prolog.

• Spring 2003 451 mid-term #1 and solutions. (Icon)

• Spring 2003 451 mid-term #2 and solutions. (Icon)

• Spring 2003 451 final exam and solutions. (Icon)

Ruby has never been taught before in 372 and therefore there are no old Ruby exams but I have included some old exams with Icon material. Some of the material, such as questions about generators and result sequences, is not applicable but the plain old programs can typically be done about as easily in Ruby as Icon. However, students were limited to Icon's built-in functions so there may be some problems that would be trivialized with Ruby's big library. Icon problems involving "string scanning" can typically be handled with regular expressions but it's not 100%.