CS 105 Computer Programming: Perl
Spring 2013 (unique # 53215)

When Mondays and Wednesdays at 1:00pm-2:00pm from January 14 through March 7
Where ECJ 1.204
Web http://www.cs.utexas.edu/~cdunham/cs105/
Instructor Curtis Dunham
Office hours by appointment only
E-mail cdunham at cs.utexas.edu (Please include cs105 in the subject)
Prerequisites CS 307, 313E, or EE 422C (or 322C) with a grade of at least C-

Course Objectives

Perl is a programming language that combines the modern robustness of Java with the expedient pragmatism of scripting languages. It offers both the low-level system access of C and the high-level elegance of Lisp. One of its mottoes is, “There’s More Than One Way To Do It.” Its flexibility makes Perl a powerful tool, but its permissiveness can lead to incomprehensible code or mysterious bugs.

This course provides a brief introduction to the language for students who want to add Perl to their toolbox. It assumes familiarity with the fundamental elements of computer programming, but no prior experience with Perl or any other particular language is necessary. Brief weekly assignments will give students hands-on experience writing, debugging, and revising Perl programs. A final project will exercise students' ability to develop a slightly more involved program, integrating concepts familiar from the weekly assignments.


No textbook is required. All assignments should be possible to complete using only the lecture notes and the Perl documentation that it specifically mentions. The perl man page is a great place to start.

However, to get the most out of this course and Perl itself, a book is a great investment. A very good (and free on the web in PDF) resource is chromatic's Modern Perl. After this course is over and you still like and/or want to use Perl, I highly recommend Effective Perl Programming by Joseph N. Hall, et al. as well as books by Damian Conway and Mark Jason Dominus.

If you find yourself wanting more examples or explanations, I highly recommend purchasing a book!


Students are encouraged to attend every lecture. While poor attendence does not guarantee poor grades, regular attendence is highly correlated with good grades. Any lecture slides or code samples presented in class will be posted to Blackboard, unless they are homework solutions. Assignments will be announced in class but not through Blackboard, unless you configure Blackboard to send notifications about new assignments.

Office Hours

Office hours will be held by appointment only, for the convenience of both student and instructor. Email me to set up a time to meet. After the GDC opens, we will probably meet in one of the common areas. I am also happy to thwart a meeting by answering your question(s) via email.


Seven weekly homeworks will be assigned, typically in Wednesday classes and due the following Wednesday. All homeworks are due at 10:00 AM (one hour before classtime) on the due date. Homework can be turned in up to 12 hours late (10:00 PM) for half credit. Homework will be submitted using the turnin program from a CS account (run man turnin on a CS machine for more details). Do not use the Microlab Turnin web page. You need to get a CS account if you don't yet have one. The instructor will run your programs on a CS machine with Perl 5.10.1. I recommend SSH for remote login since your Perl experience will be text-centric.


Each homework assignment counts as 10% of your final grade, so all homeworks will collectively count for 70%. The final project will account for the remaining 30% of the final grade and serves in lieu of a final exam. Note that the final project will be due after the class stops meeting on March 6, but office hours will continue to be available until the due date of the final project. Grades will be posted on Blackboard. The instructor reserves the right to use attendance and class participation to improve your final letter grade if you are “on the fence.” Any questions about grades must be submitted in writing (including via e-mail).

Class Announcements and Discussion

The instructor will send class announcements through Blackboard.

Blackboard also has a Discussion Board so students can help each other. Appropriate discussion topics include questions about Perl itself, requests for clarification about anything said in class, requests for help with the computing environment, etc. In general, the discussion board is for sharing information that may be of interest to classmates, but obviously homework solutions are off-limits!

Code of Conduct

See the Computer Science Department's Code of Conduct. Students are encouraged to work together to improve their understanding of the course material, but for all homework assignments, only their own work may be submitted. University policies on academic dishonesty will be strictly enforced.


1 Mon January 14 Course overview; Survey; Perl introduction; First program
2 Wed January 16 Perl basics: Data types; Variables; Sigils; Defined-ness; Truth; Control flow
Mon January 21 Martin Luther King, Jr. holiday - no class
3 Wed January 23 Perl basics: I/O; Context; String literals and quoting; Lists; Intermediate iteration
4 Mon January 28 Intermediate file I/O, array and hash manipulation; Special variables
5 Wed January 30 Advanced iteration; other print functions; Variable scoping; Functions
6 Mon February 4 Perl warning modes; Introduction to Regular Expressions; Basis in Automata
7 Wed February 6 Regular expressions: Operators, Metacharacters, Character classes, basic assertions
8 Mon February 11 Practical regular expressions; Advanced regular expressions
9 Wed February 13 References; Data structures
10 Mon February 18 Using modules and objects; Packages; Object-Oriented theory
11 Wed February 20 Tied variables; some real-world examples
12 Mon February 25 Miscellaneous helpful things
13 Wed February 27 More helpful things
14 Mon March 4 discussion of final; catch-up and/or discussion/demonstration of practical issues
15 Wed March 6 Looking ahead: Perl 6
  Tue April 2 final project due at 12 noon, no late turn-in

The instructor reserves the right to adjust this schedule if necessary.