🚀 go-pugleaf

neufeld@physics.utoronto.ca (Christopher Neufeld) wrote:

>Here's my attempt at problem #2, as a typical first year student might
>write it. The kind of student who is always right, even when he's wrong.
>Some things work by accident, some by design, few things look quite
>right. An ungenerous marker might suspect that some of the code isn't
>original, but that's typical of such students.

     Why would a marker be a student?
  a) A grad student.
  b) He's "[T]he kind of student who is always right, even when he's
wrong."

>=====

>/* This program uses a function which compares two strings, ignoring
> * case, to compare its arguments.
> *
> * Note to the stupid professor who I bet never reads these stupid
> * comments he's always asking us to put in our code: because the

     What else are TAs for?

> * problem as stated isn't very clear, I had to make this program
> * handle ***three*** different interpretations of the problem. This

     Only three?

> * had better count towards three assignments, or I'll tell all the
> * new students not to take your class and you'll lose your job. And

     Look, he isn't reading it; the TA is.  OTOH, you've just given
the TA a good chuckle and scuttlebutt to spread around the department.
This might well get the prof in trouble.

> * just in case you do read this, I'll bet you don't know that I'm
> * related to the department chairman (though he'll just deny it if
> * you ask, so that he can watch you dig your own grave).

     A byblow from his youth, perhaps?
     Note to C programmers: "byblow" should not be confused with "side
effect" despite their similiarity.
     Wasn't the scuttlebutt enough?

[snip]

Sincerely,

Gene Wirchenko

C Pronunciation Guide:
     y=x++;     "wye equals ex plus plus semicolon"
     x=x++;     "ex equals ex doublecross semicolon"