Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!convex!iex!ntvax!jbeard
From: jbeard@ntvax.uucp (Jeff Beardsley)
Newsgroups: comp.os.minix
Subject: Re: gotos
Message-ID: <1989Oct3.131847.15627@ntvax.uucp>
Date: 3 Oct 89 13:18:47 GMT
References: <24962@louie.udel.EDU> <1989Sep29.183703.1275@utzoo.uucp> <1764@psueea.UUCP>
Reply-To: jbeard@ntvax.UUCP (Jeff Beardsley)
Organization: University of North Texas
Lines: 10

Actually even the use of goto for a multi-level break/continue can easily
be avoided by taking the entire multi-level structure, making it into a 
function of its own, and using return.

This gets rid of the goto statement needed for multi-level break as well
as making the code more readable.  Therefore I believe the NO-GOTO blanket
statement *IS* a defensible position.

-- 
-------- Jeff Beardsley at UNT -----------  --------