×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, 2008-07-03 at 10:14 -0500, Francis Lapeyre wrote:
Maybe it's just me, but why chain to a record you just accessed with a
READE?
In any event, this is the usual way I do reade loops:
Setll Key_List File;
if %Equal(file);
Dou %EOF(File);
Reade Key_List File;
If %EOF(File);
Leave;
Endif;
// process your stuff here..
Enddo;
Endif;
This way, the loop is avoided if there is nothing to process.
Are you choosing to "avoid" the loop for readability or for machine
efficiency? I suggest that machine efficiency should not be a
consideration here.
I dislike unreachable code as it always raises a suspicion that I have
missed something. So FWIW, to avoid the never-satisfied condition on
the DOU, I prefer ...
Setll Key_List File;
Dow 0 = 0;
Reade Key_List File;
If %eof();
Leave:
Endif;
The virtues I see here are (1) just one input statement, (2) just one
statement to exit from the loop, and (3) the input and the test are
close together. Perhaps IBM will someday give us a single statement to
accomplish this, something like
forRecordSet [Key_List] File;
// process one record here
endFor;
Cheers,
Terry.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.