🚀 go-pugleaf

In article <41hsls$or@aadt.sdt.com> hawkins@PROBLEM_WITH_INEWS_GATEWAY_FILE (Tony Hawkins) writes
H ....
H   for iLoop: (i=0;i<10;i++)
H     {
H     for(j=0;j<10;j++)
H       {
H       /*  some other code here to set condition */
H       if(condition) break iLoop;
H       } 
H     }

This is nice, and would be just fine, except that it is not obvious hou to
make it work with "do ... while (...);"--label between "while" and "(" also?

In article <m0smnEc-000G1QC@eyrie.demon.co.uk>, Derek Fawcus <df@eyrie.demon.co.uk> writes
D    I quite like this,  esp. if there was an equivalent 'continue iLoop'
D construct available,  such that the label is available to break/continue.
D And yes,  control flow would have to be limited towards outer loops.
If we can make up a distinction between "goto"-labels and theze, the
rest can be handled by scoping: the label is known onlie within the
loop or "switch" (for the latter, of cours, onlie "break").

D ....
D    As it is at the moment,  I usually end up coding constructs like that
D as functions which return true/false values and then doing the
D break/continue based upon the return value.  Unfortunatly this can end
D up making the code harder to follow.
Yeap: this is, in effect, use of "return" for "goto".