Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: notesfiles
Path: utzoo!linus!decvax!decwrl!sun!qubix!ios!oliveb!hplabs!hp-pcd!hpcnoe!dat
From: dat@hpcnoe.UUCP (dat)
Newsgroups: net.lang.c
Subject: Re: Breaking out of several nested loops
Message-ID: <4800002@hpcnoe.UUCP>
Date: Thu, 11-Oct-84 15:27:00 EDT
Article-I.D.: hpcnoe.4800002
Posted: Thu Oct 11 15:27:00 1984
Date-Received: Tue, 23-Oct-84 05:46:22 EDT
References: <631@ihuxs.UUCP>
Organization: Hewlett-Packard - Fort Collins, CO
Lines: 25
Nf-ID: #R:ihuxs:-63100:hpcnoe:4800002:000:871
Nf-From: hpcnoe!dat    Oct 18 11:27:00 1984


	I have to agree.

	One of the biggest problems in the realm of professional
programmers (hows THAT for a concept!) (scary) is that they don't 
understand that there CAN BE EXCEPTIONS TO EVERY RULE.

	Sure it is good to try to avoid goto's like the plague, but
in some cases it IS the best possible approach.  

	My last job was with a DoD contractor and we had in writing
that we COULD NOT USE ANY GOTO's.  PERIOD.  NO EXCEPTIONS.  And we
were using Fortran VII so there weren't a whole lot of alternatives
in some cases.

	I just foisted the code that I felt necessitated the 'goto' to
someone else and bypassed the whole issue)

	What the hell - Assembler and 'Spaghetti Code' are interesting,
and a CHALLENGE to debug (especially if it ain't commented and it ain't
yours!) right?  We're getting too wimpy.  :-)

	Structuredly,
				Dave Taylor
				Colorado Networks