Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site decwrl.UUCP
Path: utzoo!linus!decvax!decwrl!asente
From: asente@decwrl.UUCP (Paul Asente)
Newsgroups: net.lang.c
Subject: Re: "Break" and other ways out of loops and switches
Message-ID: <2960@decwrl.UUCP>
Date: Thu, 25-Aug-83 14:03:44 EDT
Article-I.D.: decwrl.2960
Posted: Thu Aug 25 14:03:44 1983
Date-Received: Thu, 25-Aug-83 21:16:24 EDT
References: <357@nsc.uucp>
Organization: DEC Western Research Lab, Los Altos, CA
Lines: 14

The solution with breakflags & setbreaks & testbreaks is
cleaner than one with labelled breaks and continues?  Give
me a break! (Ug)  Labelled breaks and continues are infinitely
cleaner than that tangled mess of flags.  The advantage of
structured over unstructured programming is that structured
programming is easier to understand and follow, not that it
has no gotos.  The effect of a goto is not necessarily bad if
it is to the end of a loop or the end of a procedure.  (Do you
object to multiple "return"s in a procedure?  It's really the
same thing.)

	-paul asente