Re: Infinite Loops and Explicit Exits
From: Howard Brazee (howard_at_brazee.net)
Date: 11/02/04
- Next message: Chuck Stevens: "Re: Infinite Loops and Explicit Exits"
- Previous message: Rick Smith: "Re: Infinite Loops and Explicit Exits"
- In reply to: Chuck Stevens: "Re: Infinite Loops and Explicit Exits"
- Next in thread: Lueko Willms: "Re: Infinite Loops and Explicit Exits"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 2 Nov 2004 21:22:25 GMT
On 2-Nov-2004, "Chuck Stevens" <charles.stevens@unisys.com> wrote:
> Well, I see your point, but I'd argue that having an inline PERFORM
> statement occurring thousands of lines before its associated UNTIL, as well
> as having an EXIT PERFORM and/or an EXIT PERFORM CYCLE buried somewhere in
> the middle of those thousands of lines based on conditions that might have
> nothing whatever to do with the UNTIL, is perfectly legitimate TODAY. What
> isn't legitimate is turning those thousands of lines into a paragraph so
> that the UNTIL is closer to the PERFORM, and having *that* work, because the
> EXIT PERFORM and the EXIT PERFORM CYCLE wouldn't be legal.
Good point.
It would be useful to have a good way to exit the following PERFORM loop.
PERFORM UNTIL FILE-EOF
....
PERFORM PROCESS-RECORD
** The above paragraph grew too big, so I stuck it later in the program.
...
END-PERFORM.
PROCESS-RECORD.
...
IF WEIRD-CONDITION
Get the Hell out of Dodge
END-IF
...
- Next message: Chuck Stevens: "Re: Infinite Loops and Explicit Exits"
- Previous message: Rick Smith: "Re: Infinite Loops and Explicit Exits"
- In reply to: Chuck Stevens: "Re: Infinite Loops and Explicit Exits"
- Next in thread: Lueko Willms: "Re: Infinite Loops and Explicit Exits"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|