Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

>>One could argue that do{} should take return so it might have a value,
>>but this will definitely annoy the C programmers.

>So what.

So what is that it *already* annoys us, which is *why* we would like to 
last out of a do.  Perhaps you should be able to last out if a retval
isn't wanted (as in do {} while) but should return out if one is? 
Or maybe a last should be an undef return?

--tom