Re: exceptious "return" <-- targeted break and continue (was Re: How to eliminate GOTO?)

Article View: comp.std.c

Article #3388

#3388

From: halasz
Date: Tue, 29 Aug 1995 02:23

16 lines
1421 bytes

In article <m0smnEc-000G1QC@eyrie.demon.co.uk>, Derek Fawcus <df@eyrie.demon.co.uk> writes
+ ....
+    I quite like this,  esp. if there was an equivalent 'continue iLoop'
+ construct available,  such that the label is available to break/continue.
+ And yes,  control flow would have to be limited towards outer loops.
+ ....
+    As it is at the moment,  I usually end up coding constructs like that
+ as functions which return true/false values and then doing the
+ break/continue based upon the return value.  Unfortunatly this can end
+ up making the code harder to follow.

Yes indeed ... maibe with all this use of "return" for exceptions, it would
be good to find a construct that more naturallie kithes the caller that not
all is well; more naturallie, that is, than the use of the function-valu
for an error-return, which often happens.  Fortran s indexd RETURN was an
attempt to handle this, but ill.  Ideas?

Technical Details

Message-ID: <41ttna$8d7@caip.rutgers.edu>

Path: arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mail

References: <41glno$3a0@caip.rutgers.edu> <41gnhu$qfj@eri2.erinet.com> <m0smnEc-000G1QC@eyrie.demon.co.uk>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!caip.rutgers.edu!not-for-mail
From: halasz@caip.rutgers.edu
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: exceptious "return" <-- targeted break and continue (was Re: How to eliminate GOTO?)
Followup-To: comp.std.c
Date: 28 Aug 1995 22:23:38 -0400
Organization: Rutgers University
Message-ID: <41ttna$8d7@caip.rutgers.edu>
References: <41glno$3a0@caip.rutgers.edu> <41gnhu$qfj@eri2.erinet.com> <m0smnEc-000G1QC@eyrie.demon.co.uk>
NNTP-Posting-Host: caip.rutgers.edu

Reply to Parent Message