Re: Leave outside of DO group???

You point out another piece of code that I have completely abandoned, the IF/ELSE. With the new Select groping I cannot see myself ever coding another "Else". Rather Select, When, When, ..., Otherwise, EndSelect. Absolutely simpler to code, understand, and extend.


- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 7/23/2013 8:27 PM, CRPence wrote:

While obvious with regard to DO groups
that are standalone, most Do-groups are instead embedded in an IF\ELSE.
Like a GOTO LabelName can easily cause problems when code is changed
or copied, so too could a LEAVE in an IF, given an ELSE was added; i.e.
previously having processing continued in the implied ELSE, after adding
an ELSE the processing LEAVE likely would have been defined to continue
after the DO groups of both the IF and the ELSE.? The question mark,
because arguably [and documented as such, that] they are two distinct
non-nested Do-groups; one as part of the THEN of the IF statement and
the other as part of the ELSE which is its own separate statement. Thus
there is a possibly valid argument that the LEAVE CMDLBL(*CURRENT) would
properly go to the ELSE. If the CMDLBL() specification could extend to
a LABEL for an IF versus a LABEL for a DO statement, and all of the
DO\ENDDO under that IF were considered as one Do-group, then that could
make a LEAVE in a non-looping Do-group seem somewhat reasonable [to me].

Regards, Chuck