Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: Structured Programming
Message-ID: <9713@smoke.BRL.MIL>
Date: 25 Feb 89 08:14:32 GMT
References: <18291@adm.BRL.MIL> <9574@smoke.BRL.MIL> <226@algor2.UUCP> <5576@bsu-cs.UUCP> <26369@wlbr.EATON.COM> <89071@sun.uucp> <234@jarthur.Claremont.EDU> <18012@vax5.CIT.CORNELL.EDU>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <18012@vax5.CIT.CORNELL.EDU> btcx@vax5.cit.cornell.edu (PUT YOUR NAME HERE) writes:
>And how many times have we been burned because we forgot whether a
>loop construct will always execute once or not; and how many compiler
>bugs were based on misunderstandings like that? Mistakes of that sort
>are few when you do the loop counting in the HLL and use goto's. 

Anyone who doesn't familiarize himself with his tools can get hurt
using them.  Software engineers are almost universally in agreement
that proper control constructs reduce error, and chief among these
constructs is while...do...done in various guises.