Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mailrus!utah-gr!utah-cs!cs.utexas.edu!utastro!nather
From: nather@utastro.UUCP (Ed Nather)
Newsgroups: comp.edu
Subject: Re: looking for cheating detectors
Message-ID: <2920@utastro.UUCP>
Date: 21 Jul 88 14:52:50 GMT
References: <1403@sbcs.sunysb.edu>
Organization: U. Texas, Astronomy, Austin, TX
Lines: 22

In article <1403@sbcs.sunysb.edu>, paco@sbcs.sunysb.edu (Francisco J Romero) writes:
> 
>   I am looking for a program which detects similarities between/among C 
>   programs, and can be used to detect cheaters.  
>   Maybe
>   there are more sophisticated ways of detecting cheaters I am not aware of.
>   Any help will be appreciated.                                           
> 

What on earth are you teaching?  A class on re-inventing the wheel?  Perhaps
your students would benefit from a course on how to "cheat" -- how to find
and use code someone else has written and debugged.  That's what ALL
professional programmers do if they can manage it.  The proof of a program
is running it, and if they stole the program in its entirety, and it meets
the program requirements entirely, then more power to them!  They'll have
no trouble finding a job.

-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{backbones}!{noao,ut-sally}!utastro!nather
nather@astro.as.utexas.edu