🚀 go-pugleaf

In article <4h75gn$4rq@solutions.solon.com>, kgold@watson.ibm.com says...

[ much discussion elided ] 

> Here's when I use "break" to get out of the for loop.  Polite
> criticism is welcome.
> 
> The problem with going back to the top of the loop to check a flag
> is that the loop counter is processed before the test.  For example:
> 
>     /* returns the number that suceeded, returns MAX if failed */
> 
>     for (i = 0 ; i < MAX ; i++) {
>         if (try_something(i) == SUCCESS) {
> 	    break;
>         }
>     }
>     return(i);

That looks equivalant to:

	for (i=0;i<MAX && try_something(i)==SUCCESS; i++) {
		/* other stuff */
	}

Which is more readable often depends on the circumstances though.  In addition, if 
the condition being tested happens in the middle of the loop instead of the top 
like it is here, this transformation may not be possible.
    Later,
    Jerry.