Re: question concerning evaluate.
- From: "Chuck Stevens" <charles.stevens@xxxxxxxxxx>
- Date: Mon, 29 Aug 2005 07:39:28 -0700
> That would be because it is an incorrect assumption. :) When a WHEN
> clause is satisfied, control passes to the next *executable* statement
> in the program. (It's an OR.) A second WHEN is a conditional
> statement, not an executable one.
As I read the standard, right idea, wrong terminology. If the criteria for
a given WHEN clause are met, execution continues with the first *imperative*
statement following the WHEN (one might even say *contained within*) the
WHEN clause, and from there to the statement following END-EVALUATE (or the
implicit end of the EVALUATE statement). Note that *an* imperative
statement may consist of a *sequence of* imperative statements.
Thus, WHEN is not a *statement* at all, it's a clause of the EVALUATE. It
isn't because it's a "conditional statement" that it's not executed, it's
that the rules for WHEN basically say when you're done executing the
imperative statements associated with a WHEN you're done executing the
EVALUATE.
-Chuck Stevens
.
- References:
- question concerning evaluate.
- From: Pat Hall
- Re: question concerning evaluate.
- From: LX-i
- question concerning evaluate.
- Prev by Date: Re: [OT] Hurricane prep (Was: OT: Traffic Signals in New Mexico)
- Next by Date: Re: OT: Colour blindness [Was: Re: "Shared" procedure division code]
- Previous by thread: Re: question concerning evaluate.
- Next by thread: OT: Traffic Signals in New Mexico
- Index(es):
Relevant Pages
|