Re: How to process a file (was: Report enhancements)
From: Howard Brazee (howard_at_brazee.net)
Date: 11/02/04
- Next message: Lueko Willms: "Re: Infinite Loops and Explicit Exits"
- Previous message: Chuck Stevens: "Re: Report enhancements"
- In reply to: Lueko Willms: "How to process a file (was: Report enhancements)"
- Next in thread: Frank Swarbrick: "Re: How to process a file (was: Report enhancements)"
- Reply: Frank Swarbrick: "Re: How to process a file (was: Report enhancements)"
- Reply: Lueko Willms: "Re: How to process a file"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 2 Nov 2004 17:31:06 GMT
On 2-Nov-2004, l.willms@jpberlin.de (Lueko Willms) wrote:
> Better make it wieldy as the proper structure:
>
> READ file NEXT RECORD
> PERFORM UNTIL has-found-EOF IN FILE-STATUS-file
> OR filekey > key-limit
> do-your-processing-of-that-record
> READ file NEXT RECORD
> END-PERFORM
I remember people teaching that we shouldn't have multiple READ commands. But
the above structure is so easy, so clean, and so simple that it I have ignored
them for decades.
- Next message: Lueko Willms: "Re: Infinite Loops and Explicit Exits"
- Previous message: Chuck Stevens: "Re: Report enhancements"
- In reply to: Lueko Willms: "How to process a file (was: Report enhancements)"
- Next in thread: Frank Swarbrick: "Re: How to process a file (was: Report enhancements)"
- Reply: Frank Swarbrick: "Re: How to process a file (was: Report enhancements)"
- Reply: Lueko Willms: "Re: How to process a file"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|