Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site reed.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!reed!alexis
From: alexis@reed.UUCP (Alexis Dimitriadis)
Newsgroups: net.lang.c
Subject: Re: break, continue, return, goto
Message-ID: <2151@reed.UUCP>
Date: Sun, 17-Nov-85 21:58:57 EST
Article-I.D.: reed.2151
Posted: Sun Nov 17 21:58:57 1985
Date-Received: Tue, 19-Nov-85 04:26:40 EST
Reply-To: alexis@reed.UUCP (Alexis Dimitriadis)
Organization: Reed College, Portland, Oregon
Lines: 19

References:


  Another reason to prefer `continue' (especially) to an if-else
construction is that a continue makes it _obvious_ that nothing more
will be done to this instance of the loop.  With an if-else
construction, it is necessary to make sure there is no code between the
end of the else block and the end of the loop or function block.  This
is not too bad if Craig's suggestion to keep things small is followed,
but I still feel that a continue _adds_ clarity and makes code easier
and safer to modify.

Alexis Dimitriadis
(still at large)
-- 
_______________________________________________
  As soon as I get a full time job, the opinions expressed above
will attach themselves to my employer, who will never be rid of
them again.
				alexis @ reed
    {decvax,ihnp4,ucbcad,uw-beaver}!tektronix!reed.UUCP