Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ritcv.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!akgua!clyde!burl!hou3c!hocda!houxm!houxz!vax135!floyd!cmcl2!seismo!rochester!ritcv!kar
From: kar@ritcv.UUCP
Newsgroups: net.lang
Subject: Re: Re: Teaching students with GOTO
Message-ID: <1076@ritcv.UUCP>
Date: Tue, 29-May-84 11:33:30 EDT
Article-I.D.: ritcv.1076
Posted: Tue May 29 11:33:30 1984
Date-Received: Fri, 1-Jun-84 07:41:05 EDT
References: <5806@mcvax.UUCP> <26400011@uiucdcs.UUCP>
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 16

> Now I am not a liberal user of goto's, but I do object to impossing this kind
> of rule unless there is a corresponding rule that the instructor will never
> give any assignments in which goto's may be used appropriately.
> Daniel LaLiberte (ihnp4!uiucdcs!liberte) 

Remember, this was an introductory programming course.  Sure there are places
where using goto's make more sense than not using them, but this doesn't happen
often enough in introductory projects to worry about.  Certainly not often
enough to risk the bad habits and sloppy thinking that can result from allowing
goto's.  When you are little, you get lots of similar rules (Don't go in the
street) that are later modified when you are better able to deal with the
subtleties involved (Look both ways before crossing the street).  I submit that
the same technique makes sense when learning programming.

	Ken Reek, Rochester Institute of Technology
	{allegra,seismo}!rochester!ritcv!kar