🚀 go-pugleaf

Artyom@kansmen.com (Art Shelest) wrote:

[snipped others']

>There's a trivial conversion (best viewed with fixed pitch font):

>                                 BOOL bBreak = FALSE;
>while(..)                        while(!bBreak && ..  )
>{                                {
>   ...// text1                      ...//text 1

>   if( condition )                  bBreak = condition;
>      break;                        if( !bBreak )
>                                    {
>   ...// text2                         ...// text 2
>}                                   }
>                                 }

>I'm not saying that right side is prettier, just that such conversion is 
>always possible. In face, you can write such a convertor and run your 
>"breakful" code through it just before code reviews.
>Enclosing the loop in a set of { } brackets would localize bBreak.

     Of course it is always possible.  It is also possible for the
right-hand side to be machine language.  This does not mean that
everyone should abandon HLLs.

     The left-side is clearer.  Please view this in connection with
another ?principle of programming: procedures should not be long.
Some say a page.  I say two (as I comment and blank line more).  At
any rate, there will not be a long walk to the end of the loop.  When
I examine code, one of the first things I do is to delineate the
nesting.  It's a relief when the structure is simple and does not have
a lot of nesting.  break aids this simplicity.

>   _Art.

Sincerely,

Gene Wirchenko

C Pronunciation Guide:
     y=x++;     "wye equals ex plus plus semicolon"
     x=x++;     "ex equals ex doublecross semicolon"