Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uwmcsd1.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!uwmcsd1!jerry
From: jerry@uwmcsd1.UUCP (Jerry Lieberthal)
Newsgroups: net.cse
Subject: Re: students editing output
Message-ID: <555@uwmcsd1.UUCP>
Date: Fri, 4-Oct-85 19:01:19 EDT
Article-I.D.: uwmcsd1.555
Posted: Fri Oct  4 19:01:19 1985
Date-Received: Sat, 5-Oct-85 08:05:11 EDT
References: <685@bu-cs.UUCP> <2944@ncsu.UUCP>
Organization: U of Wi-Milwaukee, Computing Services Div
Lines: 27

>    pointers.  But we only wrote ad hoc one-shots, never generic routines
>    nor did we reuse other code.  Pascal courses could teach re-use of code,
>    perhaps at the source level, but they don't.  The problem is the
>    syllabus, not the language.
> 
> Jon Mauney,    mcnc!ncsu!mauney 
> North Carolina State University

Here at University of Wisconsin-Milwaukee, I INSIST on re-use of code in the
course that I instruct.  Because of the problems with error recovery in
Pascal I/O (such as characters where an integer or real is expected..) is
developed very early as a re-usable module for the students.  This is only
one example of common routines that are developed early in the course and
re-used over and over thru the semester.

I guess what I am saying is that Jon's comment is exactly true... most of
the problems can be traced to the syllabus ...

-- 


------------------------------------------------

	- jerry     University  of Wisconsin-Milwaukee
		    Computing Services Division
		    {ihnp4, uwvax, uwmacc}!uwmcsd1!jerry
		    uwmcsd1!jerry@wisc-rsch.ARPA