Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site k.cs.cmu.edu.ARPA Path: utzoo!linus!philabs!cmcl2!seismo!rochester!cmu-cs-pt!k.cs.cmu.edu!tecot From: tecot@k.cs.cmu.edu.ARPA (Edward Tecot) Newsgroups: net.unix Subject: Re: students editing output Message-ID: <562@k.cs.cmu.edu.ARPA> Date: Mon, 23-Sep-85 01:58:26 EDT Article-I.D.: k.562 Posted: Mon Sep 23 01:58:26 1985 Date-Received: Wed, 25-Sep-85 12:10:02 EDT Organization: Carnegie-Mellon University, CS/RI Lines: 22 Since the original request came from CMU, I thought I'd get the discussion back on track. The scope of the problem is where we have 600 students in an introductory programming course who are required to hand in a few programming assignments. Demos are unreasonable due to the size of the course. The students already hand in the assignments electronically. They are also required to demo their programs inside of a script-like shell. These students are not advanced enough to be able to impose user-interface guidelines. The problem stems from actually determining whether or not the file is an actual script, and not a fake. The solution that (to my knowledge, which is not much, since I am no longer associated with the course) is being attempted is to have the script program time-stamp the file, like rogue saves; and have the handin program check this stamp. There seems to be no other way to reasonably approach this. Suggestions in this new light are welcomed. -- _emt ----- ARPA: tecot@{CMU-CS-K.ARPA|K.CS.CMU.EDU} UUCP: {seismo|ucbvax}!cmu-cs-k!tecot "They pelted us with rocks and garbage!" Brought to you by Super Global Mega Corp .com