Re: Select/When vs. If/ElseIf

[Tony Carolla <carolla@xxxxxxxxx>]

On Thu, 30 Dec 2004 10:18:08 -0800, Joe Lee <LeeJD@xxxxxx> wrote:
> I know that I have regularly, though not frequently, wished for a Select
> like statement where each "When" clause was evaluated, regardless of
> whether the previous "When" clauses were true.

I more frequently rely on the fact that not all of the When clauses
are evaluated, than wanting the Eitherway; op.  This would force the
Break; op to be used more often, or the When clauses to become more
complex as you progress down the decision tree.  I frequently will do
the following:

       SetLL (value1:value2) FileA;
       ReadE (value1:value2) FileA;

       Select;
          When Not %Equal(FileA);
             // No exact match doc found action
          When DocState='CA';
             // California doc actions
          When DocState='NV';
             // Nevada doc actions
       EndSL;

In this example, once I am at the second When clause, I know that I
have found and read in a doc record, and I don't have to test for this
condition in addition to the others, nor would I have to include a
Break op after each condition.

I would think it would be a smaller change to add an EitherWay op than
to add a new structure type op.


-- 
"Enter any 11-digit prime number to continue..."