[plt-scheme] answers in list archive

You could augment DrScheme to record every keystroke.  Cheating cases
presumably tend to be characterized by a large paste operation,
usually at the beginning (and possibly followed by several
alpha-renamings).  Eliminating the latter avoids penalizing those who
simply prefer writing their code in a different editor.

I wonder how well Marmoset does on this, given that it does a CVS
commit on every save.

Shriram

On Tue, Dec 16, 2008 at 11:23 AM, Matthias Felleisen
<matthias at ccs.neu.edu> wrote:
>
> It leaves us with the question of how to help teachers prevent cheating when
> they assign plain book problems. -- Matthias
>
>
>
> On Dec 15, 2008, at 10:04 AM, Shriram Krishnamurthi wrote:
>
>> No, plt-scheme list is fully public.  Since list membership is not
>> limited, it doesn't make sense to limit the archive.  It's plt-edu
>> that you should not be able to get to.
>>
>> On Mon, Dec 15, 2008 at 8:59 AM, Todd O'Bryan <toddobryan at gmail.com>
>> wrote:
>>>
>>> One of my students pointed out that plt-scheme has an archive that's
>>> publicly available:
>>>
>>> http://list.cs.brown.edu/pipermail/plt-scheme/2008-April/024020.html
>>>
>>> so any help or solutions we post are only a Google away. Didn't the
>>> archives used to require a password or something?
>>>
>>> Todd
>>> _________________________________________________
>>>  For list-related administrative tasks:
>>>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>>>
>> _________________________________________________
>>  For list-related administrative tasks:
>>  http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>
>