March 2004
S M Tu W Th F S
1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
^ASSIGNED
21 22 23 24 25 26 27
^DUE
28 29 30 31
At students' request, and because the network was up and down during
the lab, your hw is simply to finish the lab4 and post your solutions.
I am particularly interested in the timings of the gawk vs perl, especially
if you do a good job (use a large input file, so you aren't just timing
the interpreter's invocation). Stars will also be awarded on the clarity
of your perl code. Many of you did enough in lab that your lab star will
also be a hw star, but I would still post my solutions if I were you.
As always in this graded part of the class, I am more interested in seeing people learn the languages and good programming style than I am interested in locking up people's solutions. We can assume that anyone in the class can look at your work once you post it. I do warn you to understand the code you find online before you use it as your own. I saw some awful perl-code grabs in the lab, and it's fairly clear to me when someone's code was originally for some other purpose and not properly adapted.
BTW, if you work on wolf.cs, there IS a way to get the system output. Instead of doing system("date"), which suppresses the output (but apparently executes the command!), you can say $_ = `date`; using back-quotes. If there are multiple lines of output, you get one long string delimited by newlines.