Why is LEAVE bad? (was: Cycle Processing vs. Doing it my way)

>And what is wrong with LEAVE? It hardly
>creates spaghetti code as the program flow
>is always in the one direction. I like to refer
>to a LEAVE as a structured GOTO!!!!!

>From a readability point of view, having multiple exit points means that you
must visually scan every line of code in the routine to see where and when
it can pop out.  This is in contrast to a routine that sets a return code
and ONLY leaves from the bottom.  You don't need to scan the entire routine
to see where you come out because there's only one exit point.

Having said that, I personally use LEAVE and ITER; especially in validity
checking routines where the alternatives are worse.  But in my vanity, I
like to believe that I _think_ about the alternatives before automatically
settling on GOTO and relatives.

  --buck
"To find fault is easy; to do better may be difficult" --Plutarch