The while(false) loop

Question

came across a neat piece of code today which had me staring for a while bcos of the while(false) clause.
it doesnt do much but can be very helpful when u have a lot of if/else if statements
do
    if ( condition1)
       //do something
       break;
    if ( condition2)
       //do something
       break;
    if ( condition3)
       //do something
       break;
}while(false);anybody else want to share any other simple but neat code tricks??

Answer 1

i have always written if/else statements just like
everybody else. its just that this looks like a good
alternative when u cant put the condition as a switch
statement or when u have a lot of if/else if
statements.Sorry, I don't see what it's good for. You still have to write all those if/else if statements. Using the while(false) idiom saves you nothing at all and makes the code confusing.
This hardly qualifies as a "Design Pattern".oh my, i would never suggest that this could be a
Design Pattern. it is just a little tweak of an
existing
(good) solutionI'm trying the best I can to throw cold water on this "tweak". It's a bad solution, IMO.
Maybe the real question is: why are you writing such long if/else if or switch statements? Could polymorphism help here?
i found it while reviewing some code. i would have to quit to avoid it :-DIf I were reviewing that code I'd recommend that this code be rewritten to take out the while(false). I'd recommend that you never use it, either.
You still haven't said what benefit it has. It doesn't shorten the if/else if or switch statement. So what, in 25 words or less, is it really doing for you except confusing things?