Homework for UCLA Computer Science 131, Winter 2013

Submit your homeworks electronically on CourseWeb.

You are expected to do your homeworks by yourself. You can share ideas and discuss general principles with others in the class, but all the code that you submit must be your own work; do not share your homework code with others. Please see Grading for more details. Consult a TA or the instructor if you have any questions about this policy.

Your programs must behave robustly. Among other things, this means they must avoid arbitrary limits on the length or number of any data structure, including symbols, strings, and line length. It is OK to impose a non-arbitrary limit, e.g., because your computer runs out of memory or because of the limited range of the Java int type, but it is not OK to impose an arbitrary limit, e.g., a limit of at most 255 characters in a symbol.

Please stick to coding styles used in the course material rather than inventing your own style, as this saves work for the grader.

Assignments are due by 23:59:59 on the specified date (i.e., one second before midnight).

The schedule is tentative and may be adjusted as the quarter progresses.

due assignment
2013-01-17 Homework 1 (OCaml)
2013-01-28 Homework 2 (OCaml)
2013-02-05 Homework 3 (Java)
2013-02-19 Homework 4 (Prolog)
2013-02-25 Homework 5 (Scheme)
2013-03-07 Project (Python)
2013-03-14 Homework 6 (JavaScript, Python, etc.)

The midterm is Thursday, 2013-02-07, during lecture.

The final exam is scheduled as per the registrar.

Please see the grading policy for how assignments are treated when late.


© 1999, 2003–2013 Paul Eggert. See copying rules.
$Id: homework.html,v 1.207 2013/03/08 06:00:25 eggert Exp $